Triple
T8304249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KVB |
E194420
|
entity |
| Predicate | safetyIntegrityLevel |
P20206
|
FINISHED |
| Object | high-integrity safety system |
—
|
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: high-integrity safety system | Statement: [KVB, safetyIntegrityLevel, high-integrity safety system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: safetyIntegrityLevel Context triple: [KVB, safetyIntegrityLevel, high-integrity safety system]
-
A.
securityLevelComponents
Indicates that a particular security level is composed of, or associated with, a specific set of component elements or factors.
-
B.
safetyRequirement
chosen
Indicates that one entity specifies or imposes conditions, standards, or measures necessary to ensure the safety of another entity or activity.
-
C.
hasStabilityLevel
Indicates that something possesses a particular degree or state of stability, often quantified or categorized along a defined scale.
-
D.
safetyGoal
Indicates that an entity is associated with a specific safety objective or target condition intended to prevent harm or reduce risk.
-
E.
sanctioningLevel
Indicates the degree or severity of formal penalties, restrictions, or disciplinary measures imposed in response to a violation or noncompliant behavior.
- 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_69ca82e613e88190bf8139669bbd0d53 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7e8b9f6081909100d1da8a078616 |
completed | March 31, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69cb70bb3a708190bc705222092da614 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:53 p.m.