Triple
T19505921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FOUNDATION Fieldbus |
E488019
|
entity |
| Predicate | HSETypicalSpeed |
P37470
|
FINISHED |
| Object | 100 Mbit/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 Mbit/s | Statement: [FOUNDATION Fieldbus, HSETypicalSpeed, 100 Mbit/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HSETypicalSpeed Context triple: [FOUNDATION Fieldbus, HSETypicalSpeed, 100 Mbit/s]
-
A.
speedClass
Indicates the categorical speed level or range assigned to an entity based on how fast it moves or operates.
-
B.
hasAverageSurfaceSpeed
Indicates the typical or mean speed at which something moves across a surface over a given period or distance.
-
C.
designedServiceSpeed
Indicates the intended or specified operational speed at which a service is designed to function.
-
D.
hasTypicalVelocity
chosen
Indicates that an entity is associated with a characteristic or commonly observed speed at which it typically moves or operates.
-
E.
speedupType
Indicates the kind or category of performance improvement achieved relative to a baseline.
- 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_69d8e8d9d1c88190b01cd78b8be49384 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63511fc688190bd1474406060fa1b |
completed | April 20, 2026, 2:15 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7bd25881908caa04eaef1f6718 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:40 p.m.