Triple
T2630206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chatr Mobile |
E59613
|
entity |
| Predicate | networkUsed |
P30353
|
FINISHED |
| Object | Rogers Communications 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: Rogers Communications network | Statement: [Chatr Mobile, networkUsed, Rogers Communications network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkUsed Context triple: [Chatr Mobile, networkUsed, Rogers Communications network]
-
A.
networkType
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.
networkServed
chosen
Indicates that a network provides connectivity or services to a particular entity or set of entities.
-
C.
network
Indicates that one entity is connected to or interacts with another through a system of relationships, communication, or information exchange.
-
D.
networkService
Indicates that one entity provides or participates in a network-based service or functionality for another entity or system.
-
E.
networkRequirement
Indicates that one entity requires access to or use of another entity’s network resources or connectivity to function or be fulfilled.
- 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_69ab4ac8596c8190b34997e73d9e991c |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abdb0e7b888190bfa5d2e33f00ec0f |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd810d7f481908e81c305772c4c14 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.