Triple

T6335785
Position Surface form Disambiguated ID Type / Status
Subject S3 E142486 entity
Predicate usesTicketValidatorType P70929 FINISHED
Object VBB/BVG ticket validators LITERAL FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: VBB/BVG ticket validators | Statement: [S3, usesTicketValidatorType, VBB/BVG ticket validators]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesTicketValidatorType
Context triple: [S3, usesTicketValidatorType, VBB/BVG ticket validators]
  • A. hasTicketIntegration
    Indicates that there is an established connection enabling ticket-related data or actions to be shared or synchronized between systems or components.
  • B. usedInE-tickets
    Indicates that something (such as a method, technology, or feature) is employed or applied within the context of electronic tickets (e-tickets).
  • C. usesIntegratedTicketValidAcrossOperators
    Indicates that an entity uses a single integrated ticket that remains valid for travel across multiple transport operators.
  • D. hasTicketRequirement
    Indicates that an entity is subject to a specific ticket or admission requirement in order for access, participation, or use to be allowed.
  • E. hasTicketFormat
    Indicates that an entity’s ticket is expressed or structured in a particular format.
  • F. None of above. chosen

Provenance (4 batches)

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_69c008d4d8e88190ad301c05b08722ac completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0654a88a881908d5cb2aa7f22c4c7 completed March 22, 2026, 9:55 p.m.
PD Predicate disambiguation batch_69c060e7e2d48190af9d004236466788 completed March 22, 2026, 9:36 p.m.
PDg Predicate description generation batch_69c064c080148190a7c3218867f1f572 completed March 22, 2026, 9:53 p.m.
Created at: March 22, 2026, 4:30 p.m.