Triple
T30812529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow central tariff zone |
E784684
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fare integration zone |
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 integration zone Context triple: [Moscow central tariff zone, instanceOf, fare integration zone]
-
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.
commuter rail zone
A commuter rail zone is a designated geographic area used to determine fares, ticketing, and service boundaries for regional passenger rail travel.
-
C.
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.
-
D.
fare-free public transport zone
A fare-free public transport zone is an area within a transit network where passengers can use public transportation services without paying a fare, typically to encourage ridership, reduce congestion, and support environmental or economic goals.
-
E.
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.
- 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_69f224b4eda48190bd212ce4f3901e56 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:43 p.m.