Triple
T5479514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IMT-2000 family |
E123435
|
entity |
| Predicate | targetDataRate |
P1376
|
FINISHED |
| Object | up to 2 Mbit/s under low mobility conditions |
—
|
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 2 Mbit/s under low mobility conditions | Statement: [IMT-2000 family, targetDataRate, up to 2 Mbit/s under low mobility conditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetDataRate Context triple: [IMT-2000 family, targetDataRate, up to 2 Mbit/s under low mobility conditions]
-
A.
dataRate
chosen
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
-
B.
dataRateGeneration
Indicates the rate at which data is produced or generated over time in a given context.
-
C.
pegRate
Indicates a fixed or controlled exchange rate at which one currency is pegged to another or to a reference value.
-
D.
mode2BitRate
Indicates the data transmission rate associated with a specific operational mode.
-
E.
targetInflationRate
Indicates the inflation level that a monetary authority aims to achieve and maintain over a specified period.
- 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.