Triple
T36987126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SA-204 |
E914994
|
entity |
| Predicate | originallyAssignedToMission |
P106644
|
FINISHED |
| Object | Apollo 1 |
E53424
|
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: Apollo 1 | Statement: [SA-204, originallyAssignedToMission, Apollo 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyAssignedToMission Context triple: [SA-204, originallyAssignedToMission, Apollo 1]
-
A.
assignedMission
Indicates that an entity has been given a specific mission or task to carry out.
-
B.
assignedToUnit
Indicates that an entity (such as a person, resource, or task) is allocated or designated to a specific unit or organizational subdivision.
-
C.
isTargetOfMission
Indicates that an entity is the intended objective or focus of a particular mission or operation.
-
D.
selectedForMission
chosen
Indicates that an entity has been chosen or assigned to participate in a particular mission.
-
E.
originalMissionStatus
Indicates the initial state or condition of a mission at the time it was first defined or launched.
- 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_69f76e8dd0408190b8b46da118ea5128 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e2c52dae4819081c1f0291a849d7d |
completed | June 26, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.