Triple
T5479834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5G NR |
E123441
|
entity |
| Predicate | targetPeakDataRate |
P1376
|
FINISHED |
| Object | up to multi-gigabit per second |
—
|
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 multi-gigabit per second | Statement: [5G NR, targetPeakDataRate, up to multi-gigabit per second]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetPeakDataRate Context triple: [5G NR, targetPeakDataRate, up to multi-gigabit per second]
-
A.
maximumBitrate
Indicates the highest data transfer rate allowed or supported for a given media stream or connection.
-
B.
dataRate
chosen
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
-
C.
usagePeak
Indicates that the usage or consumption of something reaches its highest level or intensity during a particular time or condition.
-
D.
dataRateGeneration
Indicates the rate at which data is produced or generated over time in a given context.
-
E.
movementPeak
Indicates the point in time or space at which a movement or motion reaches its maximum intensity, speed, or extent.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9248ca348190aa116cace0f9b07a |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.