Triple
T15202865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BT Group |
E363309
|
entity |
| Predicate | subsidiary |
P258
|
FINISHED |
| Object | BT Consumer |
E363310
|
NE 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: BT Consumer | Statement: [BT Group, subsidiary, BT Consumer]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BT Consumer Context triple: [BT Group, subsidiary, BT Consumer]
-
A.
BT Consumer
chosen
BT Consumer is the retail division of BT Group that provides broadband, mobile, landline, and TV services to residential customers in the UK.
-
B.
BT
BT is the vehicle registration code used on license plates for the city and district of Bayreuth in Upper Franconia, Germany.
-
C.
BT
BT is a peer-to-peer file sharing protocol widely used for distributing large amounts of data over the internet.
-
D.
BT
BT is the two-letter ISO 3166-1 alpha-2 country code assigned to Bhutan for international standardization purposes.
-
E.
BT
BT was the stock ticker symbol for Bankers Trust, a major American banking institution that played a significant role in investment banking and financial services before its acquisition by Deutsche Bank.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85a0b78bc8190b6e5ad51a2c4cfc5 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006b693a48190a6230b7b52bc8cd3 |
completed | April 15, 2026, 9:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fed3390b708190b10c876c437c72c8 |
completed | May 9, 2026, 6:24 a.m. |
Created at: April 10, 2026, 3:10 a.m.