Triple
T10114479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bloomberg Initiative for Global Road Safety |
E218322
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road safety program |
C27439
|
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 safety program Context triple: [Bloomberg Initiative for Global Road Safety, instanceOf, road safety program]
-
A.
roadway safety guideline
A roadway safety guideline is a documented set of principles, rules, and recommended practices designed to minimize traffic-related risks and enhance the safety of all road users.
-
B.
road infrastructure
Road infrastructure encompasses the physical structures, systems, and facilities—such as roads, bridges, tunnels, signage, and drainage—designed and built to support safe and efficient vehicular and pedestrian transportation.
-
C.
road traffic agreement
A road traffic agreement is a formal arrangement between parties—such as governments, municipalities, or private entities—that defines rights, responsibilities, and rules for the use, management, and regulation of road traffic within a specified area or network.
-
D.
highway funding program
A highway funding program is a structured governmental initiative that allocates financial resources for the planning, construction, maintenance, and improvement of highway infrastructure.
-
E.
public transportation security program
A public transportation security program is a coordinated set of policies, technologies, and procedures designed to protect passengers, staff, and infrastructure across transit systems from threats, crime, and disruptions.
- 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_69ca83da93fc8190b54e44bc2b34857c |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 9:04 p.m.