Triple

T37953036
Position Surface form Disambiguated ID Type / Status
Subject Luxembourg national public transport system E946792 entity
Predicate fareAbolitionTargetUsers P190231 FINISHED
Object residents 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: residents | Statement: [Luxembourg national public transport system, fareAbolitionTargetUsers, residents]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fareAbolitionTargetUsers
Context triple: [Luxembourg national public transport system, fareAbolitionTargetUsers, residents]
  • A. fareAbolitionScope
    Indicates the extent or range within which fares are eliminated or no longer charged.
  • B. fareAppliesTo
    Indicates that a specific fare is applicable to a particular trip, service, passenger category, or travel condition.
  • C. fareTypes
    Indicates the categories or kinds of fares (e.g., ticket or pricing options) that apply to a given travel or service offering.
  • D. fareType
    Indicates the category or class of fare (such as standard, discounted, or promotional) that applies to a given trip, ticket, or pricing instance.
  • E. fareDifferentiationFrom
    Indicates that one entity’s fare or pricing structure is set or adjusted in contrast to, or as a variation from, the fare associated with another entity.
  • 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_69fcc42cbac48190b8d3e4c9ce140838 completed May 7, 2026, 4:56 p.m.
PD Predicate disambiguation batch_69fcb0fc69c88190800453eb57a7e62c completed May 7, 2026, 3:34 p.m.
PDg Predicate description generation batch_69fcc42b9334819099929649b7ef68ea completed May 7, 2026, 4:56 p.m.
Created at: May 3, 2026, 4:20 p.m.