Triple
T15202916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BT Consumer |
E363310
|
entity |
| Predicate | networkTypeUsed |
P3937
|
FINISHED |
| Object | fixed broadband network |
—
|
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: fixed broadband network | Statement: [BT Consumer, networkTypeUsed, fixed broadband network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkTypeUsed Context triple: [BT Consumer, networkTypeUsed, fixed broadband network]
-
A.
networkType
chosen
Indicates the category or kind of network associated with or used by an entity (e.g., wired, wireless, virtual, or specific protocol-based networks).
-
B.
networkTypePromoted
Indicates that a particular type of network has been elevated, highlighted, or given priority status within a system or context.
-
C.
routeNetworkType
Indicates the specific kind of transportation or communication network to which a route belongs (e.g., road, rail, or air).
-
D.
networkStatus
Indicates the current operational state or connectivity condition of a network or networked system.
-
E.
canUseNetworkType
Indicates that an entity is permitted or able to operate using a specified type of network.
- 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006b693a48190a6230b7b52bc8cd3 |
completed | April 15, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69deb97ee9d881908711dbe12a55283c |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:10 a.m.