Triple
T38131283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIA Grade 2 |
E952226
|
entity |
| Predicate | safetyRequirementsBasedOn |
P20206
|
FINISHED |
| Object | vehicle speed potential |
—
|
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: vehicle speed potential | Statement: [FIA Grade 2, safetyRequirementsBasedOn, vehicle speed potential]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: safetyRequirementsBasedOn Context triple: [FIA Grade 2, safetyRequirementsBasedOn, vehicle speed potential]
-
A.
safetyRequirement
chosen
Indicates that one entity specifies or imposes conditions, standards, or measures necessary to ensure the safety of another entity or activity.
-
B.
safetyExpectation
Indicates an expected level or standard of safety that should be maintained or provided in a given context or relationship.
-
C.
safetyRationale
Indicates the reasoning or justification provided to explain how and why something is considered safe or made safe.
-
D.
hasSafetyRegulationCompliance
Indicates that an entity adheres to, satisfies, or is in conformity with specified safety regulations or standards.
-
E.
safetyProfile
Indicates the overall level and characteristics of risk or harm associated with something, typically summarizing how safe it is under specified conditions.
- 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_69f76f083548819082bd2bbf53c79e8e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:21 p.m.