Triple
T10502422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-400 |
E247703
|
entity |
| Predicate | primaryMissionDependency |
P94515
|
FINISHED |
| Object | damage assessment of STS-125 orbiter |
—
|
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: damage assessment of STS-125 orbiter | Statement: [STS-400, primaryMissionDependency, damage assessment of STS-125 orbiter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryMissionDependency Context triple: [STS-400, primaryMissionDependency, damage assessment of STS-125 orbiter]
-
A.
primaryMissionTo
Indicates that an entity has a main or principal mission directed toward or focused on another entity.
-
B.
primaryMissionProgram
Indicates that an entity serves as the main or principal program under which another entity’s mission or primary activity is organized or executed.
-
C.
relatedMission
Indicates that one mission is connected or associated with another mission in a meaningful way, such as by shared goals, context, participants, or timeline.
-
D.
laterPrimaryMission
Indicates that one mission occurs after another mission in the sequence of primary missions.
-
E.
usedByMission
Indicates that something (such as a resource, tool, or method) is utilized or employed in the execution of a particular mission.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5099c6a848190bf1d5361e9e61108 |
completed | April 7, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8e24ac8190912c9f11b8bd3084 |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe46a6448190b061bc3545835cad |
completed | April 7, 2026, 12:53 p.m. |
Created at: April 6, 2026, 12:25 p.m.