Triple
T27660941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nest Wifi |
E697119
|
entity |
| Predicate | pointFrequencyBand |
P1685
|
FINISHED |
| Object | 2.4 GHz |
—
|
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: 2.4 GHz | Statement: [Nest Wifi, pointFrequencyBand, 2.4 GHz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointFrequencyBand Context triple: [Nest Wifi, pointFrequencyBand, 2.4 GHz]
-
A.
frequencyBand
chosen
Indicates the specific range of frequencies within which a signal, measurement, or phenomenon is defined or operates.
-
B.
numberOfFrequencyBands
Indicates the relationship specifying how many distinct frequency bands are associated with or used by an entity.
-
C.
pointBandConfiguration
Indicates a specific arrangement or setup of bands or layers associated with a particular point in a structure or system.
-
D.
frequencyRegion
Indicates that something is associated with, occurs within, or is characterized by a particular range or band of frequencies.
-
E.
hasFrequencyChannels
Indicates that an entity is associated with, or operates over, one or more specific frequency channels.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 2:36 p.m.