Triple
T3416898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hop |
E72030
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional fare system |
C1687
|
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: regional fare system Context triple: [Hop, instanceOf, regional fare system]
-
A.
public transit fare payment system
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.
-
B.
public transit fare card
A public transit fare card is a reusable, stored-value or pass-based card that riders use to pay for access to buses, trains, and other public transportation services.
-
C.
fare payment system
chosen
A fare payment system is a coordinated set of processes and technologies that calculates, collects, and validates payments for transportation services from passengers.
-
D.
public transport fare zone
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.
-
E.
public transit system
A public transit system is an organized network of shared transportation services—such as buses, trains, subways, and trams—designed to move large numbers of people efficiently within and between urban and regional areas.
- 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_69ad85ad38e48190b7660c5118a35289 |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:15 p.m.