Triple
T37414671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 17 Lunar Module Challenger |
E929666
|
entity |
| Predicate | totalSurfaceEVAHours |
P51373
|
FINISHED |
| Object | about 22 hours |
—
|
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 22 hours | Statement: [Apollo 17 Lunar Module Challenger, totalSurfaceEVAHours, about 22 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totalSurfaceEVAHours Context triple: [Apollo 17 Lunar Module Challenger, totalSurfaceEVAHours, about 22 hours]
-
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.
sunshineHoursPerYear
Indicates the total number of hours in a year during which a location receives direct sunshine.
-
D.
solarArrayArea
Indicates the total surface area occupied by a solar array used for collecting solar energy.
-
E.
energySignature
Indicates the characteristic pattern or profile of energy associated with an entity, event, or interaction.
- 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_69f76ebde49481908566cd96b37ccc84 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.