Triple
T37419729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japan transport authorities |
E929816
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transport regulator |
C3209
|
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: transport regulator Context triple: [Japan transport authorities, instanceOf, transport regulator]
-
A.
road transport regulatory body
A road transport regulatory body is an authority responsible for setting, implementing, and enforcing rules, standards, and policies governing the safe, efficient, and sustainable operation of road transport systems.
-
B.
transport ministry
chosen
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.
-
C.
rail safety regulator
A rail safety regulator is an authority responsible for setting, monitoring, and enforcing safety standards and practices across railway systems to protect passengers, workers, and the public.
-
D.
transport infrastructure operator
A transport infrastructure operator is an entity responsible for managing, maintaining, and regulating transportation networks and facilities such as roads, railways, ports, or airports to ensure safe and efficient movement of people and goods.
-
E.
transportation organization
A transportation organization is an entity that plans, manages, and operates systems or services that move people or goods from one location to another.
- 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_69f76ebde49481908566cd96b37ccc84 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.