Triple
T1177512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wi‑Fi 6 |
E25061
|
entity |
| Predicate | modulationScheme |
P23647
|
FINISHED |
| Object | OFDMA |
—
|
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: OFDMA | Statement: [Wi‑Fi 6, modulationScheme, OFDMA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modulationScheme Context triple: [Wi‑Fi 6, modulationScheme, OFDMA]
-
A.
multipleAccessSchemeDownlink
Indicates that the downlink transmission uses more than one access scheme simultaneously or in combination.
-
B.
usesModulation
chosen
Indicates that one entity applies or employs a particular modulation method or scheme in relation to another entity or process.
-
C.
multipleAccessSchemeUplink
Indicates that the uplink communication uses multiple access schemes to allow multiple users or signals to share the same transmission resources.
-
D.
signallingSystem
Indicates that one entity functions as a signalling system used to transmit information or cues to another entity.
-
E.
duplexMode
Indicates whether a communication link or device operates in half-duplex or full-duplex mode, defining if data can flow in one or both directions simultaneously.
- 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_69a494267b4c819088c97a59182bf56a |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd53e4b48190abb2167f8074a6bc |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5844348190b01ac6506906ba3b |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.