Triple
T24806952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnson solids |
E620679
|
entity |
| Predicate | areConvexPolyhedra |
P157344
|
FINISHED |
| Object | true |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: true | Statement: [Johnson solids, areConvexPolyhedra, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areConvexPolyhedra Context triple: [Johnson solids, areConvexPolyhedra, true]
-
A.
areConvex
chosen
Indicates that the referenced shape or set has the property that any line segment connecting two points within it lies entirely inside it.
-
B.
isConvex
Indicates that a shape or set has the property that every line segment connecting any two points within it lies entirely inside it.
-
C.
areNonUniformConvexPolyhedra
Indicates that the related entities are convex polyhedra whose faces or structural properties are not all identical, making them non-uniform in shape or configuration.
-
D.
isUniformPolyhedron
Indicates that a polyhedron has regular polygons as faces and is vertex-transitive, so all its vertices are equivalent under the polyhedron’s symmetries.
-
E.
isZonohedron
Indicates that the subject is a convex polyhedron whose faces are all centrally symmetric polygons, i.e., a zonohedron.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 4:50 a.m.