Triple
T1123890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wi‑Fi 5 |
E24674
|
entity |
| Predicate | supportsChannelWidth |
P3989
|
FINISHED |
| Object | 20 MHz |
—
|
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: 20 MHz | Statement: [Wi‑Fi 5, supportsChannelWidth, 20 MHz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsChannelWidth Context triple: [Wi‑Fi 5, supportsChannelWidth, 20 MHz]
-
A.
supportsLinkWidth
Indicates that one entity is capable of accommodating or enabling a specified width for a link or connection between components.
-
B.
usesChannelBandwidth
Indicates that one entity consumes or occupies a portion of the available bandwidth on a communication channel.
-
C.
typicalWidth
Indicates the usual or characteristic width associated with an entity, as opposed to an exact or measured width in a specific instance.
-
D.
hasWidth
chosen
Indicates that an entity possesses a specific measurement or extent along its width dimension.
-
E.
supportsBuyingChannel
Indicates that one entity enables, allows, or is compatible with a particular buying or purchasing channel used by another entity.
- 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_69a4940712c88190aa244f3fc6070a65 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bc4bc21881909dcfe628f59f3e8c |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4749ac8190b0fbddac2e9b2586 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.