Triple
T11647038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wiener Riesenrad Betriebs- und Besitzgesellschaft |
E276801
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | operating company |
C30305
|
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: operating company Context triple: [Wiener Riesenrad Betriebs- und Besitzgesellschaft, instanceOf, operating company]
-
A.
mass transit operator
A mass transit operator is an entity responsible for managing, coordinating, and providing public transportation services such as buses, trains, or subways within a specific region or network.
-
B.
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.
-
C.
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.
-
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.
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.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:39 p.m.