Triple

T31329113
Position Surface form Disambiguated ID Type / Status
Subject Navigo fare system E798975 entity
Predicate supportsMobileTicketing GENERATED
Object yes, via NFC-enabled smartphones for some products UNRECOGNIZED GENERATED

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.

PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsMobileTicketing
Context triple: [Navigo fare system, supportsMobileTicketing, yes, via NFC-enabled smartphones for some products]
  • A. hasElectronicTicketing chosen
    Indicates that an entity supports or provides electronic ticketing for access, booking, or transactions.
  • B. hasTicketing
    Indicates that an entity provides or is associated with a system or mechanism for issuing, managing, or selling tickets.
  • C. ticketingCompatibleWith
    Indicates that two systems, services, or components can interoperate or be used together within the same ticketing or reservation workflow without conflict.
  • D. ticketTypeAccepted
    Indicates that a particular type of ticket is valid for use or accepted in a given context or by a given entity.
  • E. hasTicketIntegration
    Indicates that there is an established connection enabling ticket-related data or actions to be shared or synchronized between systems or components.
  • 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.