Triple
T19260021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1604 Tombaugh |
E481621
|
entity |
| Predicate | hasAphelion_AU |
P20361
|
FINISHED |
| Object | 2.80 |
—
|
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: 2.80 | Statement: [1604 Tombaugh, hasAphelion_AU, 2.80]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAphelion_AU Context triple: [1604 Tombaugh, hasAphelion_AU, 2.80]
-
A.
aphelionDistance
chosen
Indicates the greatest distance between an orbiting body and the star it orbits, measured at the point of aphelion in its orbit.
-
B.
hasAphelionNear
Indicates that one celestial body's aphelion (its farthest point from the object it orbits) lies close to another specified reference point or object.
-
C.
apogeeDistance_km
Indicates the distance in kilometers between an orbiting object and the central body at the farthest point (apogee) of its orbit.
-
D.
perihelionDistance
Indicates the shortest distance between an orbiting body and the Sun along its orbital path.
-
E.
maximumElongationFromSun
Indicates the greatest angular separation an object can have from the Sun as seen by an observer, typically measured in degrees along the sky.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb8858588190a04e2a01e43fb7b2 |
completed | April 20, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:28 p.m.