Triple
T6725543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 10 |
E153506
|
entity |
| Predicate | lunarPericynthionAltitude |
P24802
|
FINISHED |
| Object | about 15.6 kilometers above lunar surface |
—
|
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 15.6 kilometers above lunar surface | Statement: [Apollo 10, lunarPericynthionAltitude, about 15.6 kilometers above lunar surface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lunarPericynthionAltitude Context triple: [Apollo 10, lunarPericynthionAltitude, about 15.6 kilometers above lunar surface]
-
A.
closestApproachToMoon
chosen
Indicates the point or distance at which an object comes nearest to the Moon along its trajectory or orbit.
-
B.
perigee
Indicates the point in an object's orbit where it is closest to the body it is orbiting.
-
C.
lunarLatitude
Indicates the angular distance of a point on the Moon north or south of the lunar equator.
-
D.
orbitAltitude
Indicates the height of an object's orbit above a reference body, typically measured from the body's surface or mean radius.
-
E.
orbitalInclinationAroundMoon
Indicates the angle between an object's orbital plane and a reference plane when the object is orbiting a moon.
- 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_69c6880afb988190ad88011b48ecfcba |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d354177481908ab3cf5437c095e2 |
completed | March 27, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_69c6d08e8a2c8190ae4e8d8c039be7ce |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:08 p.m.