Triple
T11256827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verkehrsverbund Mittelsachsen |
E266458
|
entity |
| Predicate | operatesTariffZoneSystem |
P72429
|
FINISHED |
| Object | yes |
—
|
LITERAL FINISHED |
How this triple was built (2 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: yes | Statement: [Verkehrsverbund Mittelsachsen, operatesTariffZoneSystem, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesTariffZoneSystem Context triple: [Verkehrsverbund Mittelsachsen, operatesTariffZoneSystem, yes]
-
A.
hasTariffZoneSystem
Indicates that an entity uses or is governed by a defined tariff zone system for determining prices, fees, or charges.
-
B.
usesTariffSystem
Indicates that one entity applies or operates under a tariff-based system for pricing, taxation, or fees in its interactions or transactions.
-
C.
customsRegime
Indicates the specific customs treatment or regulatory framework under which goods are imported, exported, or stored.
-
D.
hasFareZoneSystem
chosen
Indicates that an entity uses or is associated with a particular fare zone system for determining travel costs or ticketing.
-
E.
shiftedTariffAuthorityTo
Indicates that decision-making power over tariffs was transferred from one entity to another.
- F. None of above.
Provenance (3 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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e935b85c819085e1abf2dd4099c5 |
completed | April 9, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69d78793c00481908a3f764b610b77a4 |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:31 p.m.