Triple
T11976870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia XL (RM-1030) |
E285061
|
entity |
| Predicate | wifiStandards |
P21310
|
FINISHED |
| Object | 802.11 b/g/n |
—
|
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 b/g/n | Statement: [Nokia XL (RM-1030), wifiStandards, 802.11 b/g/n]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wifiStandards Context triple: [Nokia XL (RM-1030), wifiStandards, 802.11 b/g/n]
-
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.
frequencyBandSupported
Indicates that an entity supports operation or functionality within a specified frequency band.
-
C.
bandAssociation
Indicates a relationship where an entity is associated with, belongs to, or is affiliated with a particular band or musical group.
-
D.
wifiAvailable
Indicates that a location, device, or context has access to a functioning Wi-Fi network.
-
E.
supportsSingleFrequencyNetworks
Indicates that an entity enables or is compatible with operating in single frequency networks, where multiple transmitters use the same frequency to provide coordinated coverage.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903acbb9081908fe7f8360057785c |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902abca70819098291aa51b593708 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.