Triple
T5771084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NB-IoT |
E127331
|
entity |
| Predicate | multipleAccessDownlink |
P23648
|
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: [NB-IoT, multipleAccessDownlink, OFDMA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: multipleAccessDownlink Context triple: [NB-IoT, multipleAccessDownlink, OFDMA]
-
A.
multipleAccessSchemeDownlink
chosen
Indicates that the downlink transmission uses more than one access scheme simultaneously or in combination.
-
B.
multipleAccessSchemeUplink
Indicates that the uplink communication uses multiple access schemes to allow multiple users or signals to share the same transmission resources.
-
C.
multipleAccess
Indicates that an entity can be accessed or used by more than one agent, user, or process, either simultaneously or sequentially.
-
D.
secondaryAccessMode
Indicates an additional, non-primary way in which an entity can be accessed, used, or interacted with.
-
E.
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.
- 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.