Triple
T26727335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AsiaSat 1 |
E673868
|
entity |
| Predicate | refurbishedFrom |
P21630
|
FINISHED |
| Object | Westar 6 |
—
|
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: Westar 6 | Statement: [AsiaSat 1, refurbishedFrom, Westar 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refurbishedFrom Context triple: [AsiaSat 1, refurbishedFrom, Westar 6]
-
A.
refurbishedAs
Indicates that an entity has been renovated, restored, or upgraded and subsequently used or designated in a new or improved form or function.
-
B.
refurbishedIn
Indicates that an entity has undergone restoration, repair, or renovation at a specific time or during a particular period.
-
C.
reforgedFrom
Indicates that something has been newly created or remade by reshaping or reworking a previous object or material.
-
D.
renovatedFrom
chosen
Indicates that one entity has been updated, improved, or restored by modifying or reworking an earlier version represented by another entity.
-
E.
rebadgedFrom
Indicates that an item has been rebranded or renamed from a previous version or source item while remaining essentially the same product.
- 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_69eecda481d08190aea69f2f7c745f56 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6180c6ba081908b82e0a76fdb94e8 |
completed | May 2, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:43 a.m.