Triple
T21191997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TD-SCDMA |
E522232
|
entity |
| Predicate | peakUplinkRate |
P45736
|
FINISHED |
| Object | 2.2 Mbit/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: 2.2 Mbit/s | Statement: [TD-SCDMA, peakUplinkRate, 2.2 Mbit/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakUplinkRate Context triple: [TD-SCDMA, peakUplinkRate, 2.2 Mbit/s]
-
A.
bandwidthCharacteristic
Indicates the relationship specifying the bandwidth-related properties or constraints associated with a connection, link, or communication channel.
-
B.
upperBandWidth
Indicates the maximum bandwidth limit or upper threshold of data transfer capacity allowed or supported in a given context.
-
C.
maximumBitrate
chosen
Indicates the highest data transfer rate allowed or supported for a given media stream or connection.
-
D.
maxTheoreticalBandwidthPerSlot
Indicates the maximum possible data transfer capacity that can be achieved per individual slot under ideal conditions.
-
E.
dataRate
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
- 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e733381f288190b3da795f62a39568 |
completed | April 21, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:07 p.m.