Triple
T22688120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rel-15 |
E560973
|
entity |
| Predicate | definesSpectrumUse |
P37271
|
FINISHED |
| Object | sub-6 GHz 5G NR bands |
—
|
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: sub-6 GHz 5G NR bands | Statement: [Rel-15, definesSpectrumUse, sub-6 GHz 5G NR bands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesSpectrumUse Context triple: [Rel-15, definesSpectrumUse, sub-6 GHz 5G NR bands]
-
A.
definesUseOf
chosen
Indicates that one entity specifies or determines how another entity is to be used or applied.
-
B.
operatedInSpectrum
Indicates that an entity functioned or carried out its operations within a specified portion or range of the electromagnetic spectrum.
-
C.
usesFrequencyReuse
Indicates that one entity applies the technique of reusing the same frequency channels across different locations or cells within a system or network.
-
D.
spectrumContains
Indicates that a given spectrum includes or exhibits a specified component, feature, or range within it.
-
E.
scopeOfUse
Indicates the range, context, or conditions under which something is intended, allowed, or applicable to be used.
- 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.