Triple
T27660937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nest Wifi |
E697119
|
entity |
| Predicate | routerBandConfiguration |
P106325
|
FINISHED |
| Object | dual‑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: dual‑band | Statement: [Nest Wifi, routerBandConfiguration, dual‑band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routerBandConfiguration Context triple: [Nest Wifi, routerBandConfiguration, dual‑band]
-
A.
bandAssociation
Indicates a relationship where an entity is associated with, belongs to, or is affiliated with a particular band or musical group.
-
B.
networkBand
chosen
Indicates the specific frequency band or range within a network over which communication or data transmission occurs.
-
C.
routingCapability
Indicates the ability of an entity to determine and direct the path that data, messages, or items should take through a network or system.
-
D.
operatedInBand
Indicates that an entity performed or was active as a member within a particular musical band.
-
E.
satelliteBand
Indicates that something operates in, uses, or is associated with a specific frequency band within the satellite communication spectrum.
- 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_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 2:36 p.m.