Triple
T11187669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dish Wireless |
E264714
|
entity |
| Predicate | MVNOOn |
P94489
|
FINISHED |
| Object | AT&T 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: AT&T network | Statement: [Dish Wireless, MVNOOn, AT&T network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MVNOOn Context triple: [Dish Wireless, MVNOOn, AT&T network]
-
A.
MVNOType
Indicates the specific category or model of mobile virtual network operator (MVNO) relationship an entity has with an underlying network provider.
-
B.
hasMVNO
chosen
Indicates that one entity operates as a Mobile Virtual Network Operator (MVNO) using the network infrastructure or services provided by another entity.
-
C.
wirelessOperator
Indicates that an entity operates, manages, or provides services for a wireless communication system or network for another entity.
-
D.
telecommunicationsProvider
Indicates that one entity provides telecommunications services (such as phone, internet, or data connectivity) to another entity.
-
E.
carrierOf
Indicates that one entity serves as the medium, vehicle, or host that contains, transports, or conveys another entity.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8ad143481908d5dacc95837ecfd |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf4461c8190af84060f7db83211 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.