Triple
T16825433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISDN |
E409006
|
entity |
| Predicate | PRITotalBitRate |
P1376
|
FINISHED |
| Object | 1.544 Mbit/s in T1 systems |
—
|
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.544 Mbit/s in T1 systems | Statement: [ISDN, PRITotalBitRate, 1.544 Mbit/s in T1 systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PRITotalBitRate Context triple: [ISDN, PRITotalBitRate, 1.544 Mbit/s in T1 systems]
-
A.
maximumBitrate
Indicates the highest data transfer rate allowed or supported for a given media stream or connection.
-
B.
pegRate
Indicates a fixed or controlled exchange rate at which one currency is pegged to another or to a reference value.
-
C.
bitrateRange
Indicates the range of data transfer rates (minimum to maximum bitrate) within which something, such as a media stream or encoding, operates.
-
D.
mode2BitRate
Indicates the data transmission rate associated with a specific operational mode.
-
E.
dataRate
chosen
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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b3126db88190ac5595b0d50e4232 |
completed | April 18, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.