Triple
T4780777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morning Star |
E106158
|
entity |
| Predicate | orbitalOrder |
P37518
|
FINISHED |
| Object | second planet from the Sun |
—
|
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: second planet from the Sun | Statement: [Morning Star, orbitalOrder, second planet from the Sun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitalOrder Context triple: [Morning Star, orbitalOrder, second planet from the Sun]
-
A.
orbitType
Indicates the specific kind or classification of an object's orbit in relation to the body it revolves around.
-
B.
orderOf
chosen
Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
-
C.
hasOrbitalDirection
Indicates that one celestial body orbits another in a specified directional sense (e.g., prograde or retrograde).
-
D.
orbits
Indicates that one object moves in a curved, usually repetitive path around another object due to a central force such as gravity.
-
E.
hasOrbitalStability
Indicates that an object maintains a stable, non-disruptive orbit around another body over time.
- 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_69bd43f3074c8190937e7b0a457fe9f1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd69237f80819090713ed62653fb75 |
completed | March 20, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69bd622be1388190ab5511b589c878c0 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.