Triple
T5771082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NB-IoT |
E127331
|
entity |
| Predicate | downlinkModulation |
P23647
|
FINISHED |
| Object | QPSK |
—
|
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: QPSK | Statement: [NB-IoT, downlinkModulation, QPSK]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: downlinkModulation Context triple: [NB-IoT, downlinkModulation, QPSK]
-
A.
multipleAccessSchemeDownlink
Indicates that the downlink transmission uses more than one access scheme simultaneously or in combination.
-
B.
usesBasebandTransmission
Indicates that one entity employs baseband transmission, meaning it sends digital signals directly over a communication medium without modulating them onto a higher-frequency carrier.
-
C.
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.
-
D.
hasCarrierFrequency
Indicates that an entity (such as a signal or transmission) is associated with a specific carrier frequency at which it is transmitted or modulated.
-
E.
usesModulation
chosen
Indicates that one entity applies or employs a particular modulation method or scheme in relation to another entity or process.
- 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_69c00834f6308190851b0abeddd8ed7e |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02acb12c081908e4beee4a957f9f9 |
completed | March 22, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69c021ce8d3c81909b332cb1c33a61ad |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:50 p.m.