Triple
T7574569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westar 6 stranded in improper orbit |
E179328
|
entity |
| Predicate | subsequentDisposition |
P13710
|
FINISHED |
| Object | sold to AsiaSat |
—
|
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: sold to AsiaSat | Statement: [Westar 6 stranded in improper orbit, subsequentDisposition, sold to AsiaSat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsequentDisposition Context triple: [Westar 6 stranded in improper orbit, subsequentDisposition, sold to AsiaSat]
-
A.
finalDisposition
Indicates the ultimate outcome, status, or resolution assigned to an entity after all relevant processes or decisions are complete.
-
B.
subsequentTreatment
Indicates that one treatment occurs after and in response to a prior treatment or medical event.
-
C.
subsequentCase
Indicates that one legal case follows another in time or procedural order, often relying on or referencing the earlier case.
-
D.
laterStatus
chosen
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
-
E.
subsequentDesignation
Indicates that one designation or status follows and replaces another in a sequence or timeline.
- 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_69c69f316e50819081a271c85c06f918 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f948e1e08190ad807292365a0c27 |
completed | March 27, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69c6f4de77048190b8769e717fdcf8e7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:51 p.m.