Triple
T30315696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iMac Pro (2017) |
E771048
|
entity |
| Predicate | wirelessStandards |
P21310
|
FINISHED |
| Object | Wi‑Fi 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 802.11ac | Statement: [iMac Pro (2017), wirelessStandards, Wi‑Fi 802.11ac]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wirelessStandards Context triple: [iMac Pro (2017), wirelessStandards, Wi‑Fi 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.
wirelessStandalone
Indicates that something operates wirelessly on its own, without needing to be connected to or dependent on another device or system.
-
C.
includesWireless
Indicates that one entity provides or comes equipped with wireless capability, connectivity, or components for another entity.
-
D.
telecomStandardSupported
Indicates that a system, device, or service is compatible with and can operate according to a specified telecommunications standard.
-
E.
usedInTelecommunicationsStandardization
Indicates that something is employed or plays a role within the processes, documents, or frameworks of telecommunications standardization.
- 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68193b2b08190a00f08dbba490563 |
completed | May 2, 2026, 10:58 p.m. |
| PD | Predicate disambiguation | batch_69f67603526c81908295a1ece8727c66 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:51 p.m.