Triple
T14257288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlin ABC fare zones |
E353417
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fare zone scheme |
C2855
|
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: fare zone scheme Context triple: [Berlin ABC fare zones, instanceOf, fare zone scheme]
-
A.
fare network
A fare network is an interconnected system of transportation routes, services, and pricing structures through which passengers can travel using coordinated tickets or payment methods.
-
B.
public transport fare zone
chosen
A public transport fare zone is a defined geographic area within a transit network used to calculate ticket prices and validate passenger fares based on the zones they travel through.
-
C.
road pricing scheme
A road pricing scheme is a system for charging drivers fees to use specific roads or areas, typically to manage congestion, reduce environmental impacts, or fund transportation infrastructure.
-
D.
ticketing zone
A ticketing zone is a designated area within a transportation or event system where specific fare or access rules apply, determining the validity and cost of tickets used within its boundaries.
-
E.
fare classification system
A fare classification system is a structured framework that categorizes transportation or ticket prices into distinct classes based on rules, restrictions, and customer or service attributes to manage pricing, availability, and revenue.
- 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:09 a.m.