Triple
T35627619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Controller Area Network |
E1029497
|
entity |
| Predicate | lowSpeedFaultTolerantSpecifiedBy |
P84847
|
FINISHED |
| Object | ISO 11898-3 |
—
|
NE NERFINISHED |
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: ISO 11898-3 | Statement: [Controller Area Network, lowSpeedFaultTolerantSpecifiedBy, ISO 11898-3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowSpeedFaultTolerantSpecifiedBy Context triple: [Controller Area Network, lowSpeedFaultTolerantSpecifiedBy, ISO 11898-3]
-
A.
effectAtLowSpeed
Indicates that the described effect or influence occurs specifically when the entity is moving or operating at a low speed.
-
B.
hasSlowMovement
Indicates that an entity exhibits movement that is slower than a normal or expected speed.
-
C.
canReduceSpeedTo
Indicates that an entity has the capability to lower its speed to a specified level or threshold.
-
D.
hasSlewRateTypical
Indicates that an entity is characterized by a specified typical (nominal) slew rate value.
-
E.
notHighSpeedLine
chosen
Indicates that the line or connection does not qualify as a high-speed line according to the relevant criteria or standards.
- 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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f15e6ac8190916822e28724534a |
completed | May 3, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.