Triple
T8286842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EDGE |
E193805
|
entity |
| Predicate | typicalUserDataRate |
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: [EDGE, typicalUserDataRate, 100–200 kbit/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalUserDataRate Context triple: [EDGE, typicalUserDataRate, 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.
dataRateGeneration
Indicates the rate at which data is produced or generated over time in a given context.
-
C.
userCount
Indicates the number of users associated with or involved in a given context or entity.
-
D.
typicalUpdateFrequency
Indicates how often an entity is usually updated or refreshed over time.
-
E.
traditionalUsers
Indicates that the associated users adhere to long-established or customary practices, methods, or preferences in the given context.
- 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_69ca82e32db481908b72f3804fa71152 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7ad3722481908076508908d18621 |
completed | March 31, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69cb70ad9fc081908741f8c4a4141edf |
completed | March 31, 2026, 6:58 a.m. |
Created at: March 30, 2026, 5:52 p.m.