Triple
T3463863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Stafford |
E73088
|
entity |
| Predicate | missionRoleApolloSoyuz |
P48933
|
FINISHED |
| Object | Apollo commander |
—
|
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: Apollo commander | Statement: [Thomas Stafford, missionRoleApolloSoyuz, Apollo commander]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionRoleApolloSoyuz Context triple: [Thomas Stafford, missionRoleApolloSoyuz, Apollo commander]
-
A.
firstMannedLunarLandingMission
Indicates that the subject is the first crewed space mission to successfully land humans on the Moon.
-
B.
missionName
Indicates the designated title or label assigned to a specific mission or operation.
-
C.
ArtemisIVMissionType
Indicates the specific category or classification of the Artemis IV mission based on its planned objectives or operational profile.
-
D.
spaceProgram
Indicates that an entity is involved in, operates, or is associated with an organized program dedicated to space exploration, research, or related activities.
-
E.
missionSpecialist
Indicates that an entity serves in the role of a mission specialist in relation to a particular mission or spaceflight.
- F. None of above. chosen
Provenance (4 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_69ad85b224d481908ff8be51338d24ff |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb0b73f481908c9f8d2b9b9bbbaf |
completed | March 8, 2026, 6:08 p.m. |
| PD | Predicate disambiguation | batch_69adae05bb0081909dc7e4779d6e05ef |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb1ecb02881908394f197e31431b4 |
completed | March 8, 2026, 5:29 p.m. |
Created at: March 8, 2026, 3:17 p.m.