Triple
T27660944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nest Wifi |
E697119
|
entity |
| Predicate | pointMU-MIMO |
P164335
|
FINISHED |
| Object | supported |
—
|
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: supported | Statement: [Nest Wifi, pointMU-MIMO, supported]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointMU-MIMO Context triple: [Nest Wifi, pointMU-MIMO, supported]
-
A.
multipleAccessSchemeUplink
Indicates that the uplink communication uses multiple access schemes to allow multiple users or signals to share the same transmission resources.
-
B.
multipleAccessSchemeDownlink
Indicates that the downlink transmission uses more than one access scheme simultaneously or in combination.
-
C.
maxSpatialStreams
Indicates the maximum number of simultaneous spatial data streams that can be used or supported in a communication or processing context.
-
D.
interferenceManagement
Indicates the management or mitigation of disruptive effects one entity’s signals or actions have on another’s performance or operation.
-
E.
multiplexing
Indicates combining multiple signals or data streams into a single channel or medium for transmission or processing.
- F. None of above. chosen
Provenance (4 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_69f644de4a84819087ddb84757fc4585 |
completed | May 2, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f643e818d481908fc66bc91bd25d77 |
completed | May 2, 2026, 6:35 p.m. |
Created at: April 27, 2026, 2:36 p.m.