Triple
T35079210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ETF (Eurovia Travaux Ferroviaires) |
E1012386
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway maintenance company |
C21077
|
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: railway maintenance company Context triple: [ETF (Eurovia Travaux Ferroviaires), instanceOf, railway maintenance company]
-
A.
railway construction company
A railway construction company is an organization that plans, designs, and builds railway infrastructure, including tracks, stations, bridges, and related systems, often coordinating engineering, procurement, and project management activities.
-
B.
rolling stock maintenance company
chosen
A rolling stock maintenance company is an organization that inspects, services, repairs, and overhauls railway vehicles such as locomotives, passenger coaches, and freight wagons to ensure their safety, reliability, and regulatory compliance.
-
C.
railway holding company
A railway holding company is a parent corporation that owns and controls one or more railway operating or infrastructure companies, managing their strategic direction and financial interests without necessarily running day-to-day train operations itself.
-
D.
rail transport company
A rail transport company is an organization that owns, operates, or manages trains and railway infrastructure to provide freight and/or passenger transportation services.
-
E.
street railway company
A street railway company is a business entity that owns, operates, and maintains streetcars or trams running on fixed rails along public streets to provide urban passenger transportation.
- 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_69f76dd32c008190853aef6028f60208 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.