Triple
T35544432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pete Conrad |
E1027165
|
entity |
| Predicate | lunarModuleRole |
P183398
|
FINISHED |
| Object | Apollo 12 Lunar Module 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 12 Lunar Module commander | Statement: [Pete Conrad, lunarModuleRole, Apollo 12 Lunar Module commander]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lunarModuleRole Context triple: [Pete Conrad, lunarModuleRole, Apollo 12 Lunar Module commander]
-
A.
lunarModulePilot
Indicates that the subject serves as the pilot of a lunar module in a space mission.
-
B.
lunarModuleCompanion
Indicates a relationship where one entity serves as a companion or partner to another in the context of a lunar module mission or activity.
-
C.
roleInApollo16
Indicates that an entity held a specific role or position in the Apollo 16 mission.
-
D.
spaceShuttleRole
Indicates the specific function or duty an entity has in relation to a space shuttle (e.g., its operational, crew, or mission role).
-
E.
primeContractorLunarModule
Indicates that an entity serves as the primary contractor responsible for developing or managing a lunar module for another entity or program.
- 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_69f76e008ba08190927acd8e5e0344c8 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f7340e4819092a1a47f7028e63f |
completed | May 3, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79ec14ce08190b22cee0b40d33743 |
completed | May 3, 2026, 7:15 p.m. |
Created at: May 3, 2026, 4:04 p.m.