Loading problem...
A geometry validation service stores side-length triplets in a table and needs a per-row triangle category.
Table: Triangles
(A, B, C) is unique per row.
For every row, assign exactly one label:
Triangle validity rule (all must hold):
Return one column:
Return rows in any order.
Supported submission environments:
Triangles:
| A | B | C |
|----|----|----|
| 20 | 20 | 23 |
| 20 | 20 | 20 |
| 20 | 21 | 22 |
| 13 | 14 | 30 |[
{"triangle_type":"Equilateral"},
{"triangle_type":"Isosceles"},
{"triangle_type":"Not A Triangle"},
{"triangle_type":"Scalene"}
](20,20,20) is Equilateral, (20,20,23) is Isosceles, (20,21,22) is Scalene, and (13,14,30) fails triangle inequality so it is Not A Triangle.
Triangles:
| A | B | C |
|---|---|---|
| 5 | 5 | 9 |
| 5 | 5 | 10|
| 7 | 9 | 12|[
{"triangle_type":"Isosceles"},
{"triangle_type":"Not A Triangle"},
{"triangle_type":"Scalene"}
]5+5>9 so the first row is a valid Isosceles triangle. 5+5=10 makes the second row degenerate and invalid. 7,9,12 are all distinct and valid, so Scalene.
Triangles:
| A | B | C |
|------------|------------|------------|
| 1000000000 | 1000000000 | 1000000000 |
| 1 | 1 | 2 |[
{"triangle_type":"Equilateral"},
{"triangle_type":"Not A Triangle"}
]Very large equal sides are still valid, while (1,1,2) violates the strict inequality requirement.
Constraints