Triple
T26529516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Demo-2 |
E670780
|
entity |
| Predicate | previousComparableMission |
P182815
|
FINISHED |
| Object | STS-135 |
—
|
NE NERFINISHED |
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-135 | Statement: [Demo-2, previousComparableMission, STS-135]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousComparableMission Context triple: [Demo-2, previousComparableMission, STS-135]
-
A.
hasPredecessorMission
Indicates that a mission occurs after and is directly preceded by another specific mission in a sequence.
-
B.
previousMissionOfOrbiter
Indicates that one mission is the immediately preceding mission undertaken by a given orbiter.
-
C.
nextMission
Indicates that one mission directly follows another in a planned or chronological sequence.
-
D.
notableSuccessorMission
Indicates that one mission is a particularly prominent or significant successor to another mission in a sequence or lineage of related missions.
-
E.
hasMissionTo
Indicates that an entity is assigned or dedicated to carrying out a specific mission, task, or purpose related to another entity or objective.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f794f24e588190965e39b77534d53f |
completed | May 3, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f791cad5e08190a8a04ca283dbecaa |
completed | May 3, 2026, 6:19 p.m. |
Created at: April 27, 2026, 1:34 a.m.