Triple
T13180175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 90482 Orcus |
E313700
|
entity |
| Predicate | hasOrbitalInclinationDegrees |
P9974
|
FINISHED |
| Object | 20.6 |
—
|
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: 20.6 | Statement: [90482 Orcus, hasOrbitalInclinationDegrees, 20.6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrbitalInclinationDegrees Context triple: [90482 Orcus, hasOrbitalInclinationDegrees, 20.6]
-
A.
targetOrbitInclination
Indicates the angle between an object's orbital plane and a reference plane (such as the equatorial or ecliptic plane) for its target orbit.
-
B.
hasOrbitalPlane
Indicates that one entity possesses or is associated with a specific orbital plane in which its orbit lies.
-
C.
orbitInclinationRange
Indicates the range of possible orbital inclination angles within which an object’s orbit is oriented relative to a reference plane.
-
D.
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.
-
E.
hasOrbitalDirection
Indicates that one celestial body orbits another in a specified directional sense (e.g., prograde or retrograde).
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc2c0c88190be357811aa8e828d |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:14 p.m.