Triple
T22766327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 11 landing site |
E563136
|
entity |
| Predicate | elevationRelativeToMeanRadius |
P149644
|
FINISHED |
| Object | approximately −2,400 m |
—
|
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 −2,400 m | Statement: [Apollo 11 landing site, elevationRelativeToMeanRadius, approximately −2,400 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationRelativeToMeanRadius Context triple: [Apollo 11 landing site, elevationRelativeToMeanRadius, approximately −2,400 m]
-
A.
distanceFromEarthCenter
Indicates the measured or calculated spatial distance between an entity and the center of the Earth.
-
B.
positionRelativeToEarth
Indicates the spatial position or orientation of an entity in relation to the Earth as a reference frame.
-
C.
hasEquatorialRadius
Indicates that an entity has a specified radius measured at its 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.
hasApproximateDistanceFromEquator
Indicates that one entity has an approximate measured or estimated distance from the Earth's equator.
- F. None of above. chosen
Provenance (4 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_69e24552e11c81909c2d61578a558bd7 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17a80e2688190b76844c408929d32 |
completed | April 29, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:26 p.m.