Triple
T33731835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 16 landing site |
E864293
|
entity |
| Predicate | orbitalCommandModulePilot |
P26362
|
FINISHED |
| Object | Thomas K. Mattingly II |
—
|
NE NERFINISHED |
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 16 landing site, orbitalCommandModulePilot, Thomas K. Mattingly II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitalCommandModulePilot Context triple: [Apollo 16 landing site, orbitalCommandModulePilot, 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.
crewModule
Indicates that an object functions as or contains a crew module, i.e., a section designed to house and support crew members.
-
C.
crewMemberInOrbit
Indicates that a person is serving as a crew member aboard a spacecraft or station that is currently in orbit.
-
D.
isPilotOf
Indicates that one entity serves as the pilot who operates or controls another entity, typically a vehicle or aircraft.
-
E.
lunarModulePilot
Indicates that the subject serves as the pilot of a lunar module in a space 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_69f3498a64cc8190b4b414c67b280d93 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb1eeb64819083f6f04633b000f2 |
completed | May 3, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:44 a.m.