Triple
T22766325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 11 landing site |
E563136
|
entity |
| Predicate | lunarLongitudeApprox |
P50427
|
FINISHED |
| Object | 23.473° E |
—
|
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: 23.473° E | Statement: [Apollo 11 landing site, lunarLongitudeApprox, 23.473° E]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lunarLongitudeApprox Context triple: [Apollo 11 landing site, lunarLongitudeApprox, 23.473° E]
-
A.
lunarLongitude
Indicates the angular position of the Moon along its orbital path, measured as longitude relative to a defined reference direction or point.
-
B.
lunarLatitude
Indicates the angular distance of a point on the Moon north or south of the lunar equator.
-
C.
selenographicLongitude
chosen
Indicates the longitudinal position of a point on the Moon’s surface measured east or west from the Moon’s prime meridian.
-
D.
celestialLongitude
Indicates the angular position of a celestial object along the ecliptic, measured eastward from a defined reference point such as the vernal equinox.
-
E.
orbitalLongitude
Indicates the angular position of an orbiting body along its orbital path, measured as longitude from a defined reference direction or point.
- 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_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. |
Created at: April 17, 2026, 3:26 p.m.