Triple
T14375952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plusnet |
E356473
|
entity |
| Predicate | partOf |
P40
|
FINISHED |
| Object | BT Consumer division |
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 division | Statement: [Plusnet, partOf, BT Consumer division]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BT Consumer division Context triple: [Plusnet, partOf, BT Consumer division]
-
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 two-letter ISO 3166-1 alpha-2 country code assigned to Bhutan for international standardization purposes.
-
C.
BT
BT is the vehicle registration code used on license plates for the city and district of Bayreuth in Upper Franconia, Germany.
-
D.
BT
BT is a major British telecommunications and network services company providing broadband, mobile, TV, and IT services in the UK and internationally.
-
E.
BT
BT is the postcode area covering Belfast and much of Northern Ireland.
- 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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de900949fc81909be0da1734c46645 |
completed | April 14, 2026, 7:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd4c5514688190be90776c8764d4f3 |
completed | May 8, 2026, 2:37 a.m. |
Created at: April 10, 2026, 1:16 a.m.