Triple
T18874445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UN Regulation No. 152 |
E461647
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international vehicle safety standard |
C5735
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: international vehicle safety standard Context triple: [UN Regulation No. 152, instanceOf, international vehicle safety standard]
-
A.
transportation standard
chosen
A transportation standard is an agreed-upon set of rules, specifications, and protocols that ensure compatibility, safety, and efficiency across transportation systems, vehicles, and infrastructure.
-
B.
international standard
An international standard is an agreed-upon set of rules, guidelines, or specifications established by recognized global bodies to ensure compatibility, safety, and quality across countries and industries.
-
C.
international vehicle registration code
An international vehicle registration code is a standardized alphabetic code displayed on motor vehicles to indicate the country in which they are registered.
-
D.
international standard series
An international standard series is a structured set of globally recognized norms or specifications, typically numbered and organized by topic, that ensure consistency, compatibility, and quality across countries and industries.
-
E.
international statistical standard
An international statistical standard is a globally agreed framework of concepts, definitions, classifications, and methods that ensures data are collected, compiled, and reported in a consistent and comparable way across countries and over time.
- F. None of above.
Provenance (1 batch)
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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 11:57 a.m.