Triple
T27660935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nest Wifi |
E697119
|
entity |
| Predicate | routerWiFiStandard |
P21310
|
FINISHED |
| Object | Wi‑Fi 5 (802.11ac) |
—
|
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: Wi‑Fi 5 (802.11ac) | Statement: [Nest Wifi, routerWiFiStandard, Wi‑Fi 5 (802.11ac)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routerWiFiStandard Context triple: [Nest Wifi, routerWiFiStandard, Wi‑Fi 5 (802.11ac)]
-
A.
supportsWiFiStandard
chosen
Indicates that one entity is compatible with and able to operate using a specified Wi-Fi communication standard defined by another entity.
-
B.
telecomStandardSupported
Indicates that a system, device, or service is compatible with and can operate according to a specified telecommunications standard.
-
C.
wirelessStandalone
Indicates that something operates wirelessly on its own, without needing to be connected to or dependent on another device or system.
-
D.
wifiAvailable
Indicates that a location, device, or context has access to a functioning Wi-Fi network.
-
E.
supportsSoftAPMode
Indicates that an entity is capable of operating in Soft Access Point (SoftAP) mode, allowing it to function as a wireless access point.
- 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_69f634a016b08190973fd3a552a9757c |
completed | May 2, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:36 p.m.