Triple
T21158488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deutsche Bahn fare zone (regional networks) |
E521371
|
entity |
| Predicate | relatedConcept |
P37
|
FINISHED |
| Object | tariff association (Verkehrsverbund) |
—
|
NE NERFINISHED |
How this triple was built (3 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: tariff association (Verkehrsverbund) | Statement: [Deutsche Bahn fare zone (regional networks), relatedConcept, tariff association (Verkehrsverbund)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: tariff association (Verkehrsverbund) Context triple: [Deutsche Bahn fare zone (regional networks), relatedConcept, tariff association (Verkehrsverbund)]
-
A.
Verkehrsverbund Ost-Region
Verkehrsverbund Ost-Region is the public transport association that coordinates and manages integrated ticketing and fares for the eastern region of Austria, including Vienna and its surrounding areas.
-
B.
Verkehrsverbund Berlin-Brandenburg
Verkehrsverbund Berlin-Brandenburg is the integrated public transport authority that coordinates and manages fares and services across Berlin and the surrounding Brandenburg region.
-
C.
Münchner Verkehrs- und Tarifverbund
The Münchner Verkehrs- und Tarifverbund is the public transport association that coordinates and manages the integrated ticketing and fare system for Munich and its surrounding region.
-
D.
Heidenheimer Tarifverbund
Heidenheimer Tarifverbund is a regional public transport tariff association in the Heidenheim area of Germany that coordinates and unifies fares across multiple transport operators.
-
E.
Hamburger Verkehrsverbund
Hamburger Verkehrsverbund is the integrated public transport association serving Hamburg and its surrounding metropolitan region in northern Germany.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: tariff association (Verkehrsverbund) Target entity description: A tariff association (Verkehrsverbund) is a regional public transport authority that coordinates and integrates fares, tickets, and timetables across multiple transport operators within a defined area.
-
A.
Verkehrsverbund Ost-Region
Verkehrsverbund Ost-Region is the public transport association that coordinates and manages integrated ticketing and fares for the eastern region of Austria, including Vienna and its surrounding areas.
-
B.
Verkehrsverbund Berlin-Brandenburg
Verkehrsverbund Berlin-Brandenburg is the integrated public transport authority that coordinates and manages fares and services across Berlin and the surrounding Brandenburg region.
-
C.
Münchner Verkehrs- und Tarifverbund
The Münchner Verkehrs- und Tarifverbund is the public transport association that coordinates and manages the integrated ticketing and fare system for Munich and its surrounding region.
-
D.
Heidenheimer Tarifverbund
Heidenheimer Tarifverbund is a regional public transport tariff association in the Heidenheim area of Germany that coordinates and unifies fares across multiple transport operators.
-
E.
Hamburger Verkehrsverbund
Hamburger Verkehrsverbund is the integrated public transport association serving Hamburg and its surrounding metropolitan region in northern Germany.
- F. None of above. chosen
Provenance (2 batches)
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_69e0b50d1ea481909c07e63c3ead9316 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7252dc3f0819094c6acf52a9f308d |
completed | April 21, 2026, 7:20 a.m. |
Created at: April 16, 2026, 2:59 p.m.