Triple
T28613195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enhanced Data rates for GSM Evolution |
E724216
|
entity |
| Predicate | typicalUserDownlinkRate |
P1376
|
FINISHED |
| Object | 100–200 kbit/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: 100–200 kbit/s | Statement: [Enhanced Data rates for GSM Evolution, typicalUserDownlinkRate, 100–200 kbit/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalUserDownlinkRate Context triple: [Enhanced Data rates for GSM Evolution, typicalUserDownlinkRate, 100–200 kbit/s]
-
A.
dataRate
chosen
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
-
B.
dataRateLowSpeed
Indicates that the data transmission rate is at a relatively low speed or bandwidth level.
-
C.
bandwidthCharacteristic
Indicates the relationship specifying the bandwidth-related properties or constraints associated with a connection, link, or communication channel.
-
D.
dataRateGeneration
Indicates the rate at which data is produced or generated over time in a given context.
-
E.
downlinkMethod
Indicates the method or technology used to transmit data from a remote system (e.g., satellite or spacecraft) down to a receiving station.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a00ccadb6908190ab810a7c05315fa8 |
completed | May 10, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_6a00cc0f86b88190a0d2c43618558f86 |
completed | May 10, 2026, 6:18 p.m. |
Created at: April 28, 2026, 4:31 a.m.