Triple
T19505919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FOUNDATION Fieldbus |
E488019
|
entity |
| Predicate | H1Speed |
P2096
|
FINISHED |
| Object | 31.25 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: 31.25 kbit/s | Statement: [FOUNDATION Fieldbus, H1Speed, 31.25 kbit/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: H1Speed Context triple: [FOUNDATION Fieldbus, H1Speed, 31.25 kbit/s]
-
A.
maxSpeed
chosen
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
B.
hasTopSpeedSection
Indicates that an entity includes or is associated with a segment or portion where the maximum or top speed is defined, reached, or relevant.
-
C.
speedClass
Indicates the categorical speed level or range assigned to an entity based on how fast it moves or operates.
-
D.
marketedSpeedName
Indicates the branded or advertised name used to describe the speed of a product or service.
-
E.
highSpeedBrand
Indicates that a brand is associated with operating or performing at high speed compared to typical or competing brands.
- 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.