Triple
T4695317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Technical Regulations under the 1998 Agreement |
E104127
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international vehicle technical regulation framework |
C2070
|
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 technical regulation framework Context triple: [Global Technical Regulations under the 1998 Agreement, instanceOf, international vehicle technical regulation framework]
-
A.
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.
-
B.
international framework
chosen
An international framework is a structured set of principles, rules, and mechanisms agreed upon by multiple countries to guide cooperation, coordination, and decision-making on shared global issues.
-
C.
transportation standard
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.
-
D.
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.
-
E.
regulatory framework
A regulatory framework is a structured set of rules, guidelines, and enforcement mechanisms established by authorities to govern behaviors, processes, and standards within a specific domain.
- 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_69bd43df91f481908e9add1b617b60ef |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:17 p.m.