Triple
T34507273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 13 |
E885921
|
entity |
| Predicate | originalCommandModulePilot |
P26362
|
FINISHED |
| Object | Thomas K. Mattingly II |
E864294
|
NE 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: Thomas K. Mattingly II | Statement: [Apollo 13, originalCommandModulePilot, Thomas K. Mattingly II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalCommandModulePilot Context triple: [Apollo 13, originalCommandModulePilot, Thomas K. Mattingly II]
-
A.
commandModulePilot
chosen
Indicates that an entity serves as the pilot of a command module in a space mission or spacecraft system.
-
B.
missionCommandModule
Indicates that one entity serves as the command module component of a mission involving the other entity.
-
C.
commandModuleFunction
Indicates that an entity serves as a command module and specifies the function or role that this command module performs.
-
D.
backupCommandModulePilot
Indicates that an entity serves as the backup pilot for a command module in place of the primary pilot.
-
E.
commanderOnBoard
Indicates that a specific individual holds the role of commanding officer on a particular vehicle, vessel, or craft during its operation.
- F. None of above.
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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37214dd6ac81908aeece08bbdf8dfe |
completed | June 20, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:01 a.m.