Triple
T30874093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaffee (lunar crater) |
E786425
|
entity |
| Predicate | namedForMission |
P179247
|
FINISHED |
| Object | Apollo 1 crew member |
—
|
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 1 crew member | Statement: [Chaffee (lunar crater), namedForMission, Apollo 1 crew member]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedForMission Context triple: [Chaffee (lunar crater), namedForMission, Apollo 1 crew member]
-
A.
isTargetOfMission
Indicates that an entity is the intended objective or focus of a particular mission or operation.
-
B.
missionName
Indicates the designated title or label assigned to a specific mission or operation.
-
C.
intendedMission
Indicates that one entity is the planned or designated mission, task, or objective associated with another entity.
-
D.
selectedForMission
Indicates that an entity has been chosen or assigned to participate in a particular mission.
-
E.
hasNamesakeMission
Indicates that one entity has a mission named after it or sharing its name.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7201e241c819092d56a7bb99dc94d |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71f8df5d48190944fbfbd9d573868 |
completed | May 3, 2026, 10:12 a.m. |
Created at: April 29, 2026, 8:48 p.m.