Triple
T37391100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 17 Command and Service Module America |
E928709
|
entity |
| Predicate | finalApolloLunarMission |
P12730
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Apollo 17 Command and Service Module America, finalApolloLunarMission, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalApolloLunarMission Context triple: [Apollo 17 Command and Service Module America, finalApolloLunarMission, true]
-
A.
lastLunarLandingMission
chosen
Indicates that the mission is the most recent one in which a spacecraft successfully landed on the Moon.
-
B.
lunarMission
Indicates a mission or operation specifically directed toward exploring, studying, or traveling to the Moon.
-
C.
lunarMissionCommanded
Indicates that an entity served as the commanding leader of a specified lunar mission.
-
D.
plannedFirstCrewedLunarLandingMission
Indicates that an entity is designated as the mission planned to perform the first crewed landing on the Moon.
-
E.
missionSequenceLunarLanding
Indicates that one event or action occurs as part of the ordered sequence of steps leading to or comprising a lunar landing mission.
- 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_69f76ebb10c481909b54b9dba263e29f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff1f3f94fc819095955299f50ab4ce |
completed | May 9, 2026, 11:49 a.m. |
| PD | Predicate disambiguation | batch_69ff1ea47748819082f63d9b9d9c3e65 |
completed | May 9, 2026, 11:46 a.m. |
Created at: May 3, 2026, 4:16 p.m.