Triple
T22688188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Licensed Assisted Access |
E560975
|
entity |
| Predicate | primaryUnlicensedBand |
P149254
|
FINISHED |
| Object | 5 GHz band |
—
|
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: 5 GHz band | Statement: [Licensed Assisted Access, primaryUnlicensedBand, 5 GHz band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryUnlicensedBand Context triple: [Licensed Assisted Access, primaryUnlicensedBand, 5 GHz band]
-
A.
primaryBand
Indicates that one band is the main or most significant band associated with an entity, as opposed to any secondary or side projects.
-
B.
secondaryBand
Indicates that an entity serves as an additional or supporting band associated with another primary band or musical act.
-
C.
operatedInBand
Indicates that an entity performed or was active as a member within a particular musical band.
-
D.
usesBand
Indicates that one entity employs or makes use of a particular band (such as a group, frequency band, or band resource) in performing an action or fulfilling a function.
-
E.
frequencyBand
Indicates the specific range of frequencies within which a signal, measurement, or phenomenon is defined or operates.
- 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_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. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:13 p.m.