Triple
T28856813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Working Party on Road Transport (SC.1) |
E728760
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road transport regulatory body |
C55310
|
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: road transport regulatory body Context triple: [Working Party on Road Transport (SC.1), instanceOf, road transport regulatory body]
-
A.
state transport department
A state transport department is a government agency responsible for planning, regulating, and managing transportation systems and infrastructure within a state, including roads, public transit, and vehicle services.
-
B.
transportation safety agency
A transportation safety agency is an organization responsible for regulating, monitoring, and enforcing safety standards across transportation systems to prevent accidents and protect the public.
-
C.
transport ministry
The transport ministry is a government department responsible for planning, regulating, and overseeing a nation’s transportation systems and infrastructure, including roads, railways, air, and maritime transport.
-
D.
state transportation board
A state transportation board is a governing body that oversees planning, funding, and policy decisions for a state’s transportation systems and infrastructure.
-
E.
public transit safety oversight agency
A public transit safety oversight agency is a governmental or quasi-governmental body responsible for setting, monitoring, and enforcing safety standards and practices across public transportation systems to protect passengers, workers, and the public.
- F. None of above. chosen
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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:45 a.m.