Triple
T33839542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 15 landing site |
E867321
|
entity |
| Predicate | primaryLunarModulePilot |
P26363
|
FINISHED |
| Object | James B. Irwin |
E291611
|
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: James B. Irwin | Statement: [Apollo 15 landing site, primaryLunarModulePilot, James B. Irwin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryLunarModulePilot Context triple: [Apollo 15 landing site, primaryLunarModulePilot, James B. Irwin]
-
A.
lunarModulePilot
chosen
Indicates that the subject serves as the pilot of a lunar module in a space mission.
-
B.
firstDockingAstronaut
Indicates that the subject is the astronaut who first docked with the specified target (such as a spacecraft, station, or module).
-
C.
lunarModuleRole
Indicates the specific function or responsibility an entity has in relation to a lunar module within a mission or system.
-
D.
Apollo1Crewmate
Indicates that one entity is a member of the crew of the Apollo 1 space mission in relation to another entity.
-
E.
roleInApollo16
Indicates that an entity held a specific role or position in the Apollo 16 mission.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a375bc2fe9c8190b24a2f8369817cbc |
completed | June 21, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:47 a.m.