Triple
T4007576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AT&T Broadband |
E89561
|
entity |
| Predicate | brandFate |
P3146
|
FINISHED |
| Object | brand discontinued after Comcast acquisition |
—
|
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: brand discontinued after Comcast acquisition | Statement: [AT&T Broadband, brandFate, brand discontinued after Comcast acquisition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brandFate Context triple: [AT&T Broadband, brandFate, brand discontinued after Comcast acquisition]
-
A.
fate
chosen
Indicates that an entity is destined or predetermined to experience a particular outcome or course of events beyond its control.
-
B.
brand
Indicates that one entity is the commercial brand or label under which another entity (such as a product, service, or organization) is marketed or identified.
-
C.
fateLocation
Indicates the location where an entity ultimately ends up or meets its final outcome.
-
D.
afterlifeFate
Indicates the outcome or condition an entity experiences in the afterlife as a result of its life or actions.
-
E.
formerBrand
Indicates that an entity was previously used or recognized as a brand for another entity but is no longer its current brand.
- 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_69aed9585e788190bec2d39deba3750f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaec08dc8190a341809059554f84 |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fa6fec81909b1190ecbba61410 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:34 p.m.