Triple
T2293407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 8 |
E51555
|
entity |
| Predicate | apoapsisAltitudeMoon |
P18900
|
FINISHED |
| Object | approximately 312 kilometers |
—
|
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: approximately 312 kilometers | Statement: [Apollo 8, apoapsisAltitudeMoon, approximately 312 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: apoapsisAltitudeMoon Context triple: [Apollo 8, apoapsisAltitudeMoon, approximately 312 kilometers]
-
A.
orbitApogee
chosen
Indicates the point in an orbit where an orbiting body is farthest from the central body it revolves around.
-
B.
perigee
Indicates the point in an object's orbit where it is closest to the body it is orbiting.
-
C.
aphelionDistance
Indicates the greatest distance between an orbiting body and the star it orbits, measured at the point of aphelion in its orbit.
-
D.
closestApproachToMoon
Indicates the point or distance at which an object comes nearest to the Moon along its trajectory or orbit.
-
E.
orbitAltitude
Indicates the height of an object's orbit above a reference body, typically measured from the body's surface or mean radius.
- 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_69a88b09c644819090b503456d96bf70 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abcd0e42248190ada33b84d75caa64 |
completed | March 7, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69abc589295c819092989820c2b4e9d8 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:48 p.m.