Triple
T1186572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wi‑Fi 6E |
E25260
|
entity |
| Predicate | spectrumRange |
P7244
|
FINISHED |
| Object | 5.925–7.125 GHz (region‑dependent) |
—
|
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.925–7.125 GHz (region‑dependent) | Statement: [Wi‑Fi 6E, spectrumRange, 5.925–7.125 GHz (region‑dependent)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spectrumRange Context triple: [Wi‑Fi 6E, spectrumRange, 5.925–7.125 GHz (region‑dependent)]
-
A.
spectralRegion
chosen
Indicates the portion of the electromagnetic spectrum (e.g., wavelength or frequency range) in which a measurement, observation, or property is defined or applies.
-
B.
typicalRange
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
C.
spectralResolution
Indicates the fineness with which a system can distinguish or separate different wavelengths or frequencies within a spectrum.
-
D.
typicalEnergyRange
Indicates the usual or characteristic range of energy values associated with an entity, process, or interaction.
-
E.
range
Indicates that a value, property, or effect extends between specified limits or over a specified interval or scope.
- 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_69a49427d98881908646d6c63b8cea1e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd5578b08190bbe4089857fbf166 |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb59ca6c81908597a81646674aaa |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.