Triple
T10208570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bell Fibe |
E242267
|
entity |
| Predicate | bundleWith |
P43695
|
FINISHED |
| Object | Bell Home Phone |
E812087
|
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: Bell Home Phone | Statement: [Bell Fibe, bundleWith, Bell Home Phone]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bell Home Phone Context triple: [Bell Fibe, bundleWith, Bell Home Phone]
-
A.
Bell
Bell is a suburban railway station in Melbourne, Australia, serving the Mernda line in the city’s northern suburbs.
-
B.
Bell
Bell is a small, predominantly working-class city in southeastern Los Angeles County, California, known for its location in the Gateway Cities region and past municipal corruption scandals.
-
C.
Bell
Bell is a common English surname notably associated with inventor Alexander Graham Bell, pioneer of the telephone.
-
D.
Bell Wireline
Bell Wireline is a major telecommunications division of BCE Inc. that provides traditional landline, internet, and related network services.
-
E.
Bell (telecommunications company)
chosen
Bell is a major Canadian telecommunications company providing phone, internet, television, and wireless services nationwide.
- 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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d395fa86cc8190b4f115b5a0f99772 |
completed | April 6, 2026, 11:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d652cca9c081909f705365c70db009 |
completed | April 8, 2026, 1:06 p.m. |
Created at: April 6, 2026, 10:59 a.m.