Triple
T1999897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Railtrack |
E43444
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rail infrastructure company |
C6404
|
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 infrastructure company Context triple: [Railtrack, instanceOf, rail infrastructure company]
-
A.
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.
-
B.
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.
-
C.
national railway company
A national railway company is a state-owned or state-controlled organization responsible for operating and managing a country's primary passenger and freight rail transport services and infrastructure.
-
D.
private railway company
A private railway company is a non-governmental business entity that owns, operates, or manages rail transport services for passengers and/or freight, typically for profit under regulatory oversight.
-
E.
transport infrastructure operator
chosen
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.
- 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_69a88715dbbc8190b2299e29e955d997 |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:37 p.m.