Triple
T12007252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | freight division of Comboios de Portugal |
E285812
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | division of railway company |
C13555
|
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: division of railway company Context triple: [freight division of Comboios de Portugal, instanceOf, division of railway company]
-
A.
railroad operating division
chosen
A railroad operating division is a geographically defined segment of a railway system managed as a unit for train operations, crew assignments, dispatching, and maintenance activities.
-
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.
group of railway companies
A group of railway companies is an organized association of multiple rail transport operators that collaborate or are collectively managed to provide coordinated rail services, share resources, or pursue common commercial or regulatory interests.
-
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.
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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:46 p.m.