Triple
T6439263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LTE-Advanced |
E129975
|
entity |
| Predicate | maximumTheoreticalDownlinkRate |
P45736
|
FINISHED |
| Object | 1 Gbit/s |
—
|
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 Gbit/s | Statement: [LTE-Advanced, maximumTheoreticalDownlinkRate, 1 Gbit/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumTheoreticalDownlinkRate Context triple: [LTE-Advanced, maximumTheoreticalDownlinkRate, 1 Gbit/s]
-
A.
maxSpatialStreams
Indicates the maximum number of simultaneous spatial data streams that can be used or supported in a communication or processing context.
-
B.
maximumBitrate
chosen
Indicates the highest data transfer rate allowed or supported for a given media stream or connection.
-
C.
dataRate
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
-
D.
supportsBandwidths
Indicates that an entity is compatible with or can operate using the specified range or set of bandwidth values.
-
E.
maxDataTransferMode
Indicates the data transfer mode in which the maximum possible data throughput is achieved between entities.
- 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.