Triple
T2977135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ixion |
E80424
|
entity |
| Predicate | hasOrbitalEccentricity |
P2030
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Ixion, hasOrbitalEccentricity, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrbitalEccentricity Context triple: [Ixion, hasOrbitalEccentricity, high]
-
A.
orbitalEccentricity
Indicates the degree to which an orbit deviates from a perfect circle, quantifying how elongated the orbital path is.
-
B.
hasOrbitalPeriod
Indicates that one entity completes a full orbit around another entity within a specified duration.
-
C.
hasEccentricity
chosen
Indicates that an object or orbit possesses a specific degree of deviation from being perfectly circular, quantified by its eccentricity value.
-
D.
hasOrbitalPlane
Indicates that one entity possesses or is associated with a specific orbital plane in which its orbit lies.
-
E.
hasInnermostStableCircularOrbit
Indicates that one entity specifies the radius or location of the innermost stable circular orbit associated with another entity (typically in a gravitational or relativistic system).
- 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.