Triple

T19927287
Position Surface form Disambiguated ID Type / Status
Subject Varketili E478957 entity
Predicate fareSystem P395 FINISHED
Object Metromoney card NE NERFINISHED

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: Metromoney card | Statement: [Varketili, fareSystem, Metromoney card]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Metromoney card
Context triple: [Varketili, fareSystem, Metromoney card]
  • A. Metromoney card chosen
    The Metromoney card is a rechargeable contactless smart card used to pay for public transportation in Tbilisi, Georgia.
  • B. Metcard
    Metcard was Melbourne’s former magnetic stripe ticketing system used for public transport before the introduction of the Myki smartcard.
  • C. Leap Card
    Leap Card is a reusable, contactless smart card used for paying public transport fares across Dublin and other parts of Ireland.
  • D. Presto card
    The Presto card is a reloadable smart card used for paying public transit fares across the Greater Toronto and Hamilton Area and other regions in Ontario, Canada.
  • E. Credo Card
    Credo Card is a core service philosophy tool used by The Ritz-Carlton Hotel Company to communicate and reinforce its brand standards, values, and commitment to exceptional guest service among employees.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e521855c8190b41871700afc8d6a completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e659ca52c881908dc8053bf61be4c4 completed April 20, 2026, 4:52 p.m.
Created at: April 10, 2026, 1:53 p.m.