Triple
T8612108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I2C |
E203934
|
entity |
| Predicate | standardSpeed |
P53843
|
FINISHED |
| Object | 100 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 kbit/s | Statement: [I2C, standardSpeed, 100 kbit/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardSpeed Context triple: [I2C, standardSpeed, 100 kbit/s]
-
A.
recommendedSpeed
chosen
Indicates the speed that is advised or suggested as appropriate under given conditions, rather than required or actual speed.
-
B.
standardPar
Indicates that two entities are parallel and conform to a recognized or defined standard of parallelism.
-
C.
standardNumber
Indicates that an entity is associated with a canonical or officially recognized reference number used for identification or classification.
-
D.
typicalSpeedup
Indicates the usual or expected performance improvement (e.g., reduction in time or increase in speed) achieved when applying one method, system, or configuration relative to another.
-
E.
currentSpeed
Indicates the present rate at which an entity is moving over time.
- 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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46fdf21c81908ffc6363e98ab871 |
completed | March 31, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cc455437488190b7506f820daf6e32 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:25 p.m.