Triple
T16115113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Direction de la circulation ferroviaire |
E390983
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rail traffic management organization |
C3982
|
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: rail traffic management organization Context triple: [Direction de la circulation ferroviaire, instanceOf, rail traffic management organization]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
railway infrastructure manager
chosen
A railway infrastructure manager is an entity responsible for the planning, construction, maintenance, operation, and safe management of railway tracks, signaling systems, and related fixed installations.
-
E.
rail transit
Rail transit is a public transportation system that moves passengers or freight along fixed steel tracks using trains, subways, trams, or light rail vehicles, typically in urban or intercity corridors.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
Created at: April 10, 2026, 5 a.m.