Triple
T18257704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PROFINET RT |
E437258
|
entity |
| Predicate | latencyRange |
P45126
|
FINISHED |
| Object | sub-millisecond |
—
|
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: sub-millisecond | Statement: [PROFINET RT, latencyRange, sub-millisecond]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: latencyRange Context triple: [PROFINET RT, latencyRange, sub-millisecond]
-
A.
communicationLatency
chosen
Indicates the time delay between when a communication is sent by one entity and when it is received or processed by another.
-
B.
algorithmicDelay
Indicates a time lag or postponement that arises specifically from the execution or processing steps of an algorithm.
-
C.
typicalRuntimeRange
Indicates the usual lower and upper bounds of time typically required for an entity to run or complete its operation.
-
D.
operationalRange
Indicates the span of conditions (such as distance, time, or environment) within which a system, device, or process can function effectively and safely.
-
E.
validityRange
Indicates the time period or contextual conditions during which something is considered valid or in effect.
- 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4fd8879e88190893f8da7c3529496 |
completed | April 19, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.