Triple
T33731842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 16 landing site |
E864293
|
entity |
| Predicate | totalEVAOnSurfaceHours |
P51373
|
FINISHED |
| Object | 20.23 |
—
|
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: 20.23 | Statement: [Apollo 16 landing site, totalEVAOnSurfaceHours, 20.23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totalEVAOnSurfaceHours Context triple: [Apollo 16 landing site, totalEVAOnSurfaceHours, 20.23]
-
A.
surfaceEVAStartTimeUTC
Indicates the coordinated universal time (UTC) at which a surface extravehicular activity (EVA) begins.
-
B.
crewEVAHours
chosen
Indicates the total number of hours that crew members spend performing extravehicular activities (spacewalks) outside their vehicle or habitat.
-
C.
evaDuration
Indicates the length of time that an extravehicular activity (EVA) lasts or is scheduled to last.
-
D.
sunshineHoursPerYear
Indicates the total number of hours in a year during which a location receives direct sunshine.
-
E.
hasAverageSurfaceSpeed
Indicates the typical or mean speed at which something moves across a surface over a given period or distance.
- 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_69f3498a64cc8190b4b414c67b280d93 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 1, 2026, 1:44 a.m.