Triple
T36987126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SA-204 |
E914994
|
entity |
| Predicate | originallyAssignedToMission |
—
|
GENERATED |
| Object | Apollo 1 |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
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 (1 batch)
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. |
Created at: May 3, 2026, 4:14 p.m.