Triple
T2977142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ixion |
E80424
|
entity |
| Predicate | hasGeneralShape |
P40719
|
FINISHED |
| Object | approximately spherical |
—
|
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: approximately spherical | Statement: [Ixion, hasGeneralShape, approximately spherical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeneralShape Context triple: [Ixion, hasGeneralShape, approximately spherical]
-
A.
hasApproximateShape
chosen
Indicates that one entity has a shape that is similar to, but not exactly the same as, the shape of another entity.
-
B.
hasIrregularShape
Indicates that an entity possesses a form or outline that deviates from a regular, standard, or symmetrical shape.
-
C.
hasSilhouetteShape
Indicates that one entity has the overall outline or contour shape specified or characterized by another entity.
-
D.
shaped
Indicates that one entity has given form, contour, or structure to another entity or outcome.
-
E.
baseShape
Indicates that one entity serves as the fundamental or underlying shape or form upon which another entity is defined, derived, or constructed.
- 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_69ad8b15f6ac8190be5fd16a33edcb4f |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad998c589c8190b4530f3fb8975187 |
completed | March 8, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69ad96105a708190a9ec4838cbcb1207 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:58 p.m.