Triple
T2977145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ixion |
E80424
|
entity |
| Predicate | hasSurfaceComposition |
P44361
|
FINISHED |
| Object | mixture of ices and darker materials |
—
|
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: mixture of ices and darker materials | Statement: [Ixion, hasSurfaceComposition, mixture of ices and darker materials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurfaceComposition Context triple: [Ixion, hasSurfaceComposition, mixture of ices and darker materials]
-
A.
hasSurfaceForm
Indicates that an abstract concept, entity, or linguistic unit is realized or expressed in a specific textual or lexical form.
-
B.
hasSurfaceSections
Indicates that an entity is composed of or divided into distinct sections or parts of its surface.
-
C.
hasPrimarySurface
Indicates that one entity serves as the main or principal surface associated with another entity.
-
D.
surfaceType
Indicates the kind or classification of surface associated with an entity or interaction.
-
E.
notableSurface
Indicates that one entity is a surface or exterior of particular significance or prominence in relation to another entity.
- 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_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. |
| PDg | Predicate description generation | batch_69ad97f5d28c8190899d90204dc43428 |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:58 p.m.