Triple
T27660936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nest Wifi |
E697119
|
entity |
| Predicate | pointWiFiStandard |
P21310
|
FINISHED |
| Object | Wi‑Fi 5 (802.11ac) |
—
|
NE NERFINISHED |
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, pointWiFiStandard, Wi‑Fi 5 (802.11ac)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointWiFiStandard Context triple: [Nest Wifi, pointWiFiStandard, 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.
typeOfAccessPoint
Indicates the specific kind or category of access point involved in the relationship or action.
-
C.
modernAccessPoint
Indicates that an entity serves as a contemporary or up-to-date point of entry, connection, or interaction for accessing another entity or resource.
-
D.
isAccessPointOf
Indicates that one entity serves as an access point or entry interface through which another entity can be reached, used, or connected to.
-
E.
isBorderAccessPoint
Indicates that a location serves as an official point where passage across a border between two regions or jurisdictions is permitted or controlled.
- 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.