Triple
T31329240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navigo Liberté+ (pay-as-you-go) |
E798979
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public transport fare product |
C13844
|
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: public transport fare product Context triple: [Navigo Liberté+ (pay-as-you-go), instanceOf, public transport fare product]
-
A.
transit fare product
chosen
A transit fare product is a purchasable medium (such as a ticket, pass, or stored value) that grants a rider the right to access and use public transportation services under specified conditions.
-
B.
public transport pricing scheme
A public transport pricing scheme is a structured set of rules and fares that determines how passengers are charged for using public transit services based on factors such as distance, time, mode, and user category.
-
C.
multimodal transport platform
A multimodal transport platform is an integrated system that coordinates and optimizes the planning, booking, and management of journeys across multiple transportation modes (such as rail, road, air, and sea) through a unified digital interface.
-
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 transport ticket
A public transport ticket is a proof-of-payment token, physical or digital, that grants an individual the right to use specified public transportation services for a defined route, time period, or fare zone.
- 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_69f224e3238c8190b2291f50ea4962cd |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:16 p.m.