Triple
T22766377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tranquility Base |
E563137
|
entity |
| Predicate | surfaceEVAStartDate |
P120464
|
FINISHED |
| Object | 1969-07-21 |
—
|
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: 1969-07-21 | Statement: [Tranquility Base, surfaceEVAStartDate, 1969-07-21]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceEVAStartDate Context triple: [Tranquility Base, surfaceEVAStartDate, 1969-07-21]
-
A.
EVAstartDate
chosen
Indicates the date on which an extravehicular activity (EVA) begins.
-
B.
surfaceAtStart
Indicates that an entity is located on or in contact with a specified surface at the beginning of a defined event or time interval.
-
C.
lastSurfaceEVAByHumans
Indicates that the referenced event is the most recent extravehicular activity conducted by humans on a planetary or moon surface.
-
D.
surfaceMissionStart
Indicates the point in time or event when a mission or operation on a surface (such as a planetary or lunar surface) begins.
-
E.
crewEVAHours
Indicates the total number of hours that crew members spend performing extravehicular activities (spacewalks) outside their vehicle or habitat.
- 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.