Triple
T35506520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orcus–Vanth system |
E1026163
|
entity |
| Predicate | hasInclinationToEcliptic |
P9974
|
FINISHED |
| Object | about 20 degrees |
—
|
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: about 20 degrees | Statement: [Orcus–Vanth system, hasInclinationToEcliptic, about 20 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInclinationToEcliptic Context triple: [Orcus–Vanth system, hasInclinationToEcliptic, about 20 degrees]
-
A.
inclinationToEcliptic
chosen
Indicates the angle between an object's orbital plane and the plane of the ecliptic, describing how tilted its orbit is relative to Earth's orbital plane.
-
B.
hasEclipticLatitude
Indicates that one celestial object or point has a specified angular distance north or south of the ecliptic plane.
-
C.
containsEcliptic
Indicates that one spatial region or object fully or partially includes the ecliptic within its extent or boundaries.
-
D.
inclinationToEarthEquator
Indicates the angle between an object's orbital or rotational plane and Earth's equatorial plane.
-
E.
liesOnEcliptic
Indicates that the referenced object’s position is located on or very close to the plane of the ecliptic.
- 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a006ef900148190ba52daf566882a03 |
completed | May 10, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_6a006c76ae748190bfe466d7d17d321e |
completed | May 10, 2026, 11:31 a.m. |
Created at: May 3, 2026, 4:04 p.m.