Triple
T1146360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saturn |
E23575
|
entity |
| Predicate | hasMeanDistanceFromSun_km |
P2016
|
FINISHED |
| Object | 1430000000 |
—
|
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: 1430000000 | Statement: [Saturn, hasMeanDistanceFromSun_km, 1430000000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMeanDistanceFromSun_km Context triple: [Saturn, hasMeanDistanceFromSun_km, 1430000000]
-
A.
hasMeanDistanceFromSun
chosen
Indicates that an entity (typically a celestial body) is characterized by a specific average distance from the Sun.
-
B.
distanceFromEarth
Indicates the measured or calculated spatial separation between an entity and the planet Earth.
-
C.
SunDistanceFromCenter
Indicates the distance between the Sun and the central reference point of a specified system (such as a galaxy or coordinate frame).
-
D.
innerBoundaryDistanceFromSun
Indicates the distance from the Sun to the inner boundary of a specified region or zone.
-
E.
aphelionDistance
Indicates the greatest distance between an orbiting body and the star it orbits, measured at the point of aphelion in its orbit.
- 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_69a493ef399c8190b04b9146d2314f59 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bd0bed00819091d71983d787a030 |
completed | March 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4ee3988190ac89c5ae5b10e316 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.