Triple

T24933781
Position Surface form Disambiguated ID Type / Status
Subject Metcard E623257 entity
Predicate usedLanguageOnTickets P79126 FINISHED
Object English 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: English | Statement: [Metcard, usedLanguageOnTickets, English]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedLanguageOnTickets
Context triple: [Metcard, usedLanguageOnTickets, English]
  • A. usesLanguageFor
    Indicates that an entity employs a particular language as a tool or medium to perform some activity, function, or purpose.
  • B. usesLanguageAs
    Indicates that one entity communicates or operates using another entity as its language or linguistic medium.
  • C. hasCustomerServiceLanguage
    Indicates that an entity provides customer service in a specified language or set of languages.
  • D. languageOfIssue chosen
    Indicates the language in which a particular item, document, or resource is issued or published.
  • E. eligibleLanguage
    Indicates that a particular language satisfies the required conditions to be considered valid or allowed in a given context.
  • 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_69e2fac6b5a48190a1c38857f00915a9 completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f464b4c9b0819085daa00c7c3b8b76 completed May 1, 2026, 8:30 a.m.
PD Predicate disambiguation batch_69f45cf017a88190b4985b11159c907d completed May 1, 2026, 7:57 a.m.
Created at: April 18, 2026, 5:30 a.m.