Triple
T34415568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verkehrsgemeinschaft Westmecklenburg |
E883394
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transport tariff association |
C40779
|
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: transport tariff association Context triple: [Verkehrsgemeinschaft Westmecklenburg, instanceOf, transport tariff association]
-
A.
fare association
A fare association represents the defined relationship between multiple fare components, rules, or pricing conditions that together determine the total cost and applicability of a travel transaction.
-
B.
regional transport association
A regional transport association is an organization that coordinates, plans, and manages public transportation services across a defined geographic area, integrating multiple operators, modes, and fare systems.
-
C.
transportation organization
A transportation organization is an entity that plans, manages, and operates systems or services that move people or goods from one location to another.
-
D.
tariff association
chosen
A tariff association is an organized group, often of businesses or carriers, that collaboratively develops, maintains, and publishes standardized rate schedules, rules, and conditions for services such as transportation or utilities.
-
E.
transport association in Switzerland
A transport association in Switzerland is a regional organization that coordinates and integrates public transportation services, fares, and timetables across multiple operators within a defined area to provide seamless mobility for passengers.
- 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_69f349c2e3b88190a67834eb5bcffeaf |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:59 a.m.