Triple
T3660731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pixel 3a |
E77640
|
entity |
| Predicate | WiFi |
P21310
|
FINISHED |
| Object | 802.11 a/b/g/n/ac |
—
|
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: 802.11 a/b/g/n/ac | Statement: [Pixel 3a, WiFi, 802.11 a/b/g/n/ac]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: WiFi Context triple: [Pixel 3a, WiFi, 802.11 a/b/g/n/ac]
-
A.
wifiAvailable
Indicates that a location, device, or context has access to a functioning Wi-Fi network.
-
B.
supportsWiFiStandard
chosen
Indicates that one entity is compatible with and able to operate using a specified Wi-Fi communication standard defined by another entity.
-
C.
network
Indicates that one entity is connected to or interacts with another through a system of relationships, communication, or information exchange.
-
D.
connectivity
Indicates...the existence, degree, or quality of a link or communication pathway between entities, allowing interaction or information flow between them.
-
E.
bandAssociation
Indicates a relationship where an entity is associated with, belongs to, or is affiliated with a particular band or musical group.
- 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_69ad85dfc4dc8190a441864202ab2a7a |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3d6fa188190a6db5bdae7083573 |
completed | March 8, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69adb847e9d881909dad2ffd0f3b6c15 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:25 p.m.