Triple

T20314766
Position Surface form Disambiguated ID Type / Status
Subject Hamburg–Copenhagen E510349 entity
Predicate ticketingIntegratedWith P52742 FINISHED
Object Deutsche Bahn long-distance fares 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: Deutsche Bahn long-distance fares | Statement: [Hamburg–Copenhagen, ticketingIntegratedWith, Deutsche Bahn long-distance fares]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ticketingIntegratedWith
Context triple: [Hamburg–Copenhagen, ticketingIntegratedWith, Deutsche Bahn long-distance fares]
  • A. ticketingCompatibleWith
    Indicates that two systems, services, or components can interoperate or be used together within the same ticketing or reservation workflow without conflict.
  • B. hasTicketing
    Indicates that an entity provides or is associated with a system or mechanism for issuing, managing, or selling tickets.
  • C. ticketingScope
    Indicates the range or domain within which ticketing actions (such as creation, assignment, or management of tickets) are valid or applicable.
  • D. hasTicketIntegration chosen
    Indicates that there is an established connection enabling ticket-related data or actions to be shared or synchronized between systems or components.
  • E. ticketingProduct
    Indicates a relationship where an entity is associated with, or offered as, a ticketing-related product (such as a service or item used for issuing, managing, or selling tickets).
  • F. None of above.

Provenance (3 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_69e0b4c7491c8190961113c4283b10b0 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e67786f4dc8190b02a6c2a4338362d completed April 20, 2026, 6:59 p.m.
PD Predicate disambiguation batch_69e55b21b09081909e46691b6f45a07f completed April 19, 2026, 10:45 p.m.
Created at: April 16, 2026, 11:19 a.m.