Triple

T37953049
Position Surface form Disambiguated ID Type / Status
Subject Luxembourg national public transport system E946792 entity
Predicate ticketingSystemBefore2020 P189662 FINISHED
Object integrated national tariff system 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: integrated national tariff system | Statement: [Luxembourg national public transport system, ticketingSystemBefore2020, integrated national tariff system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ticketingSystemBefore2020
Context triple: [Luxembourg national public transport system, ticketingSystemBefore2020, integrated national tariff system]
  • A. ticketSystem
    Indicates a relationship where an entity is managed, tracked, or processed through a ticket-based system for handling requests, issues, or tasks.
  • B. primaryTicketingSystem
    Indicates that one ticketing system is designated as the main or default system used for handling tickets in a given context.
  • C. ticketingSystemOperator
    Indicates that one entity operates, manages, or administers the ticketing system used for issuing, tracking, or processing tickets for another entity or context.
  • D. ticketSystemType
    Indicates the type or category of ticketing system associated with an entity or interaction.
  • E. ticketingTreatment
    Indicates how an entity is handled or processed within a ticketing or issue-tracking workflow.
  • 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_69f76ef64cf08190ad3e1114b62aac67 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fbc7b78f9481909f4f8fc2e3fdcde1 completed May 6, 2026, 10:59 p.m.
PD Predicate disambiguation batch_69fbbd18c9908190928d274f8731dfa8 completed May 6, 2026, 10:13 p.m.
PDg Predicate description generation batch_69fbc7b6c2c88190ad4f58980834053c completed May 6, 2026, 10:59 p.m.
Created at: May 3, 2026, 4:20 p.m.