Triple
T34643609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 12 landing site |
E889635
|
entity |
| Predicate | missionCommandModulePilot |
P26362
|
FINISHED |
| Object | Richard F. Gordon Jr. |
—
|
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: Richard F. Gordon Jr. | Statement: [Apollo 12 landing site, missionCommandModulePilot, Richard F. Gordon Jr.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionCommandModulePilot Context triple: [Apollo 12 landing site, missionCommandModulePilot, Richard F. Gordon Jr.]
-
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.
missionPilot
Indicates that an entity serves as the pilot responsible for operating or navigating a specific mission.
-
D.
missionModules
Indicates that certain modules, components, or elements are assigned to, included in, or associated with a particular mission.
-
E.
crewModule
Indicates that an object functions as or contains a crew module, i.e., a section designed to house and support crew members.
- 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_69f349d825c88190bfc6170ac9281260 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 1, 2026, 2:04 a.m.