Triple
T10502415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-400 |
E247703
|
entity |
| Predicate | reasonForPlanning |
P89710
|
FINISHED |
| Object | risk of irreparable damage to 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: risk of irreparable damage to STS-125 orbiter | Statement: [STS-400, reasonForPlanning, risk of irreparable damage to STS-125 orbiter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForPlanning Context triple: [STS-400, reasonForPlanning, risk of irreparable damage to STS-125 orbiter]
-
A.
planning
Indicates that an entity is engaged in organizing or devising a future action, event, or course of behavior involving another entity or entities.
-
B.
reasonForCreation
Indicates that one entity was created for the purpose, cause, or motivation specified by another entity.
-
C.
statedReason
Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
-
D.
reasonForUse
Indicates that one entity specifies the justification, purpose, or motivation for using another entity.
-
E.
planningBasis
chosen
Indicates that one entity serves as the foundational reference or justification used by another entity when making plans or preparing actions.
- F. None of above.
Provenance (3 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. |
Created at: April 6, 2026, 12:25 p.m.