Triple
T10735088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NJ Transit fare zones |
E253175
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | distance-based pricing system |
C4038
|
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: distance-based pricing system Context triple: [NJ Transit fare zones, instanceOf, distance-based pricing system]
-
A.
dynamic pricing facility
A dynamic pricing facility is a system or component that automatically adjusts prices in real time based on factors such as demand, supply, customer behavior, and market conditions.
-
B.
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.
-
C.
transponder-based toll system
A transponder-based toll system is an automated electronic toll collection method where vehicles equipped with small radio-frequency devices are detected and charged as they pass through toll points without stopping.
-
D.
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.
-
E.
public transit fare payment system
chosen
A public transit fare payment system manages the calculation, collection, validation, and tracking of passenger payments across various transit services and media (e.g., cards, mobile apps, tickets) to authorize and record travel.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:14 p.m.