Triple
T22688185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Licensed Assisted Access |
E560975
|
entity |
| Predicate | usesRadioAccessTechnology |
P121569
|
FINISHED |
| Object | 4G LTE |
—
|
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: 4G LTE | Statement: [Licensed Assisted Access, usesRadioAccessTechnology, 4G LTE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRadioAccessTechnology Context triple: [Licensed Assisted Access, usesRadioAccessTechnology, 4G LTE]
-
A.
hasRadio
Indicates that an entity is equipped with or includes a radio device.
-
B.
usesTelecommunications
Indicates that one entity communicates with or transmits information to another by means of telecommunications technologies or networks.
-
C.
accessTechnology
chosen
Indicates that one entity uses, supports, or is connected via a particular communication or network access technology.
-
D.
containsRadioSource
Indicates that one entity includes or encompasses a radio source within its spatial or structural extent.
-
E.
hasRadioStation
Indicates that one entity possesses, operates, or is served by a particular radio station.
- 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178983fc8819080aa00e45ff77952 |
completed | April 29, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:13 p.m.