Triple
T24023821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feve |
E594896
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | narrow-gauge railway operator |
C5965
|
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: narrow-gauge railway operator Context triple: [Feve, instanceOf, narrow-gauge railway operator]
-
A.
narrow-gauge railway line
A narrow-gauge railway line is a railroad whose track gauge is significantly smaller than the standard gauge, typically used in regions with difficult terrain, lower construction costs, or specialized transport needs.
-
B.
narrow-gauge railway terminus
A narrow-gauge railway terminus is the end station or final stopping point on a railway line that uses tracks of narrower width than the standard gauge, where trains begin or conclude their journeys and related operations are managed.
-
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.
private railway company
chosen
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.
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.
- 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 9:52 p.m.