Triple
T36703748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SM4 |
E906299
|
entity |
| Predicate | backupMission |
P186180
|
FINISHED |
| Object | STS-400 rescue mission (never flown) |
—
|
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: STS-400 rescue mission (never flown) | Statement: [SM4, backupMission, STS-400 rescue mission (never flown)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: backupMission Context triple: [SM4, backupMission, STS-400 rescue mission (never flown)]
-
A.
backupFeatureIn
Indicates that one feature serves as a backup or fallback for another feature within a given context or system.
-
B.
backupCommander
Indicates that one entity serves as the designated backup or alternate commander for another entity.
-
C.
returnMission
Indicates that an entity goes back to its original location or base after completing a mission or task.
-
D.
backupCrewAssignment
Indicates that one entity is designated to serve as a backup crew for another entity, ready to assume its duties if needed.
-
E.
missionBackboneFor
Indicates that one entity serves as the core supporting structure or essential foundation enabling the mission or primary purpose of another entity.
- 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_69f76e7195c48190b5580c9cfb01e95f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:12 p.m.