Triple
T7834880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tracking and Data Relay Satellite-B |
E181665
|
entity |
| Predicate | failedToReach |
P30122
|
FINISHED |
| Object | geosynchronous transfer orbit |
—
|
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: geosynchronous transfer orbit | Statement: [Tracking and Data Relay Satellite-B, failedToReach, geosynchronous transfer orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: failedToReach Context triple: [Tracking and Data Relay Satellite-B, failedToReach, geosynchronous transfer orbit]
-
A.
failedOn
chosen
Indicates that an attempted action or process did not succeed when applied to a specific target, condition, or step.
-
B.
missionFailure
Indicates that an attempted mission or operation did not achieve its intended objectives or outcome.
-
C.
failureCause
Indicates that one event, condition, or factor is the reason or source that caused a particular failure to occur.
-
D.
escapeAttempt
Indicates an action where an entity tries to get away from confinement, control, or a restricting situation.
-
E.
experiencedFailure
Indicates that an entity has undergone or encountered a failure in performing an action, achieving a goal, or maintaining a desired state.
- 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_69ca8284a25c8190a1a20afad30da792 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb064b872081908e269f4fe1b85436 |
completed | March 30, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69cae91e98988190abd4ece75932c589 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:45 p.m.