Triple
T16177119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zürcher Verkehrsverbund |
E392591
|
entity |
| Predicate | usesFareStructure |
P32811
|
FINISHED |
| Object | zones and fare levels |
—
|
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: zones and fare levels | Statement: [Zürcher Verkehrsverbund, usesFareStructure, zones and fare levels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFareStructure Context triple: [Zürcher Verkehrsverbund, usesFareStructure, zones and fare levels]
-
A.
partOfFareStructure
Indicates that one element is included as a component within a larger fare structure or pricing scheme.
-
B.
fareSystem
Indicates a relationship where a system is used to determine, collect, or manage fares or payments for transportation or similar services.
-
C.
fareStructure
chosen
Indicates the pricing scheme or set of rules that determine how fares are calculated and applied for a given service or trip.
-
D.
hasFareZoneSystem
Indicates that an entity uses or is associated with a particular fare zone system for determining travel costs or ticketing.
-
E.
fareSystemFeature
Indicates that a fare system possesses or supports a particular feature, function, or characteristic related to how fares are calculated, managed, or used.
- 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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e22059e7048190b4592cb1516b5f8d |
completed | April 17, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.