Triple
T1077350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LTE |
E23868
|
entity |
| Predicate | channelBandwidthOptions |
P21683
|
FINISHED |
| Object | 1.4 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: 1.4 MHz | Statement: [LTE, channelBandwidthOptions, 1.4 MHz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: channelBandwidthOptions Context triple: [LTE, channelBandwidthOptions, 1.4 MHz]
-
A.
usesChannelBandwidth
chosen
Indicates that one entity consumes or occupies a portion of the available bandwidth on a communication channel.
-
B.
channelOrder
Indicates the sequence or priority assigned to channels relative to one another.
-
C.
dataRate
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
-
D.
memoryBandwidth
Indicates the rate at which data can be transferred to or from a memory system over a given period of time.
-
E.
congestionControlAlgorithm
Indicates that one entity uses, implements, or is associated with a particular congestion control algorithm in managing network traffic.
- 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b94288d88190aae4fb86236c0702 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73ba8208190be7f3cef8c18689b |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.