Triple
T27645993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BOCs |
E696713
|
entity |
| Predicate | divestedFrom |
P10639
|
FINISHED |
| Object | AT&T long-distance operations |
—
|
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: AT&T long-distance operations | Statement: [BOCs, divestedFrom, AT&T long-distance operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divestedFrom Context triple: [BOCs, divestedFrom, AT&T long-distance operations]
-
A.
divested
chosen
Indicates that one entity has sold off, relinquished, or otherwise disposed of ownership, control, or interest in another entity or asset.
-
B.
withdrewFrom
Indicates that one entity removed itself or its participation from another entity, context, or arrangement it was previously part of.
-
C.
divestiturePartner
Indicates that one entity is a partner or counterparty involved in another entity’s divestiture transaction or process.
-
D.
delisted
Indicates that an entity has been removed from an official list, registry, or exchange where it was previously included.
-
E.
removedFrom
Indicates that one entity has been taken away, extracted, or detached from another entity or context.
- 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_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f63195d7808190a4d4bde80e99d31d |
completed | May 2, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:29 p.m.