Triple
T12007251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | freight division of Comboios de Portugal |
E285812
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rail freight operator |
C2967
|
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 operator Context triple: [freight division of Comboios de Portugal, instanceOf, rail freight operator]
-
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.
freight railroad company
chosen
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.
-
C.
freight railroad
A freight railroad is a rail transport system dedicated to moving goods and commodities—such as raw materials, manufactured products, and containers—using freight trains over a network of tracks.
-
D.
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.
-
E.
common carrier railroad
A common carrier railroad is a rail transport company that offers freight and/or passenger services to the general public under legal obligation to serve all customers without discrimination, according to published rates and schedules.
- 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:46 p.m.