Triple
T1686015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Platonic solids |
E36442
|
entity |
| Predicate | faceType |
P31336
|
FINISHED |
| Object | congruent regular polygons |
—
|
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: congruent regular polygons | Statement: [Platonic solids, faceType, congruent regular polygons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: faceType Context triple: [Platonic solids, faceType, congruent regular polygons]
-
A.
faceValueType
Indicates the type or category of a financial instrument’s face (nominal) value, such as how that value is defined or represented.
-
B.
faceExpression
Indicates the specific facial expression an entity is displaying, capturing its visible emotional or expressive state.
-
C.
frontType
Indicates the type or category of a front (e.g., boundary or leading side) that one entity presents or forms relative to another.
-
D.
facesChallenge
Indicates that an entity is confronted with a difficulty, obstacle, or demanding situation that must be dealt with or overcome.
-
E.
facedBy
Indicates that one entity is oriented toward and directly opposite another entity, such that it is facing it.
- F. None of above. chosen
Provenance (4 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_69a886151508819084fa7f1ce6e05577 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf3359ce48190803b322db8ad6027 |
completed | March 6, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69aa61b71cec8190b273588051058ebd |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69aaf33347e48190a32b6d0099e3d389 |
completed | March 6, 2026, 3:30 p.m. |
Created at: March 4, 2026, 7:29 p.m.