Triple
T27813572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North American locomotive market |
E702599
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rail industry sector |
C53392
|
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 industry sector Context triple: [North American locomotive market, instanceOf, rail industry sector]
-
A.
passenger rail operating sector
The passenger rail operating sector comprises organizations and systems responsible for providing scheduled rail transport services for people, including train operations, customer service, safety management, and coordination with infrastructure owners and regulators.
-
B.
railway industry body
A railway industry body is an organization that represents, coordinates, and sets standards or policies for companies and stakeholders involved in the rail transport sector.
-
C.
rail transportation infrastructure
Rail transportation infrastructure encompasses the physical and organizational systems—such as tracks, stations, signaling, power supply, and related facilities—required to support the safe and efficient movement of trains and rail-based services.
-
D.
industrial railway
An industrial railway is a specialized rail system used within or between industrial facilities to transport raw materials, goods, and equipment efficiently as part of production and logistics operations.
-
E.
rail transport manufacturer
A rail transport manufacturer is a company that designs, engineers, and produces railway vehicles and related equipment such as locomotives, passenger cars, freight wagons, and signaling systems.
- F. None of above. chosen
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_69ef840a16748190926719ab96120bae |
completed | April 27, 2026, 3:43 p.m. |
Created at: April 27, 2026, 5:44 p.m.