Triple
T6439271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LTE-Advanced |
E129975
|
entity |
| Predicate | supportsChannelBandwidth |
P48289
|
FINISHED |
| Object | up to 20 MHz per carrier |
—
|
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: up to 20 MHz per carrier | Statement: [LTE-Advanced, supportsChannelBandwidth, up to 20 MHz per carrier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsChannelBandwidth Context triple: [LTE-Advanced, supportsChannelBandwidth, up to 20 MHz per carrier]
-
A.
supportsBandwidths
chosen
Indicates that an entity is compatible with or can operate using the specified range or set of bandwidth values.
-
B.
usesChannelBandwidth
Indicates that one entity consumes or occupies a portion of the available bandwidth on a communication channel.
-
C.
hasFullBandwidthChannels
Indicates that the subject possesses communication channels that operate at the maximum or designated full data transmission capacity.
-
D.
hasGainBandwidthProductTypical
Indicates that an entity has a specified typical value for its gain–bandwidth product, describing the standard frequency–gain performance characteristic.
-
E.
supportsChannels
Indicates that one entity is capable of handling, providing, or being compatible with one or more specified channels for communication, distribution, or operation.
- 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_69c0084caac48190a7bc2ad8ba44536f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c06967241c8190965bac395adf2d03 |
completed | March 22, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69c060f96980819091bab9335922a457 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:45 p.m.