Triple
T37288059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arc Infrastructure |
E925587
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rail freight network operator |
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 freight network operator Context triple: [Arc Infrastructure, instanceOf, rail freight network operator]
-
A.
rail freight brand
A rail freight brand is the distinct identity, including name, visual design, reputation, and service promise, that differentiates a company providing cargo transportation by rail from its competitors.
-
B.
freight railroad network
A freight railroad network is an interconnected system of rail lines, terminals, and supporting infrastructure designed to transport goods and raw materials efficiently between industrial, commercial, and logistical hubs.
-
C.
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.
-
D.
freight railroad company
A freight railroad company is an organization that owns or operates rail infrastructure and rolling stock to transport goods and commodities by train between industrial, commercial, and logistics locations.
-
E.
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.
- 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_69f76eafe20c8190856d3b996a4c31a7 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.