Triple
T24023861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Renfe Alquiler de Material Ferroviario |
E594897
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway rolling stock leasing company |
C46571
|
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: railway rolling stock leasing company Context triple: [Renfe Alquiler de Material Ferroviario, instanceOf, railway rolling stock leasing company]
-
A.
rolling stock leasing company
chosen
A rolling stock leasing company owns and maintains railway vehicles such as locomotives and carriages, which it rents to train operators under various contractual arrangements.
-
B.
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.
-
C.
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.
-
D.
rolling stock maintenance company
A rolling stock maintenance company is an organization that inspects, services, repairs, and overhauls railway vehicles such as locomotives, passenger coaches, and freight wagons to ensure their safety, reliability, and regulatory compliance.
-
E.
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.
- 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.