Triple
T11187682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dish Wireless |
E264714
|
entity |
| Predicate | spectrumHoldings |
P97753
|
FINISHED |
| Object | U.S. spectrum licenses for 5G deployment |
—
|
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: U.S. spectrum licenses for 5G deployment | Statement: [Dish Wireless, spectrumHoldings, U.S. spectrum licenses for 5G deployment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spectrumHoldings Context triple: [Dish Wireless, spectrumHoldings, U.S. spectrum licenses for 5G deployment]
-
A.
typicalHoldingsType
Indicates the usual or most common category of holdings associated with an entity or account.
-
B.
eraOfMajorHoldings
Indicates the historical time period during which the primary or most significant holdings associated with an entity were established or predominant.
-
C.
mediaHoldingsInclude
Indicates that a collection of media assets or rights contains or encompasses the specified media item(s).
-
D.
portfolioHeldBy
Indicates that a particular portfolio is owned, managed, or maintained by a specified entity.
-
E.
sharesHeldBy
Indicates that a specified number or portion of shares is owned or held by a particular entity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69d77062271c8190b63da714ab5beff9 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:29 p.m.