Triple
T5480887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5G System |
E123462
|
entity |
| Predicate | supportsFrequencyRange |
P61515
|
FINISHED |
| Object | sub-6 GHz 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 bands | Statement: [5G System, supportsFrequencyRange, sub-6 GHz bands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsFrequencyRange Context triple: [5G System, supportsFrequencyRange, sub-6 GHz bands]
-
A.
supportsSingleFrequencyNetworks
Indicates that an entity enables or is compatible with operating in single frequency networks, where multiple transmitters use the same frequency to provide coordinated coverage.
-
B.
hasFrequencyCategory
Indicates that something is associated with a particular classification of how often it occurs or is used.
-
C.
hasBroadcastFrequency
Indicates that an entity operates or transmits at a specified broadcast frequency.
-
D.
supportsSubbands
chosen
Indicates that one entity provides or is compatible with multiple subbands within a broader frequency or spectral band.
-
E.
supportsWavelengthRange
Indicates that an entity is capable of operating over, handling, or being compatible with a specified range of wavelengths.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd93e5d0f08190a6cc9fc408b7c5bb |
completed | March 20, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69bd91a73b148190a865243536a4fe76 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.