Triple

T1514764
Position Surface form Disambiguated ID Type / Status
Subject Amsterdam Metro network E32093 entity
Predicate usesTicketingSystem P1740 FINISHED
Object OV-chipkaart E28408 NE 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: OV-chipkaart | Statement: [Amsterdam Metro network, usesTicketingSystem, OV-chipkaart]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: OV-chipkaart
Context triple: [Amsterdam Metro network, usesTicketingSystem, OV-chipkaart]
  • A. OV-chipkaart chosen
    OV-chipkaart is the nationwide contactless smart card system used for paying public transport fares across the Netherlands.
  • B. OPUS card
    The OPUS card is a reusable, contactless smart card used for public transit fare payment across the greater Montreal area and other regions in Quebec.
  • C. TAP card
    The TAP card is a reusable contactless smart card used to pay fares across public transit systems in the Los Angeles County region.
  • D. Viva Viagem smart card
    The Viva Viagem smart card is a rechargeable contactless travel card used for public transportation across the Lisbon metropolitan area, including metro, buses, trams, and some regional trains.
  • E. Opal card
    The Opal card is a reusable, contactless smartcard used to pay for public transport across much of New South Wales, Australia.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69a885e8caf88190a5fbb6159ce87786 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a907da75388190bfbdbedbd46adbdc completed March 5, 2026, 4:34 a.m.
NED1 Entity disambiguation (via context triple) batch_69ad23429f1c81909f435030de687675 completed March 8, 2026, 7:20 a.m.
Created at: March 4, 2026, 7:26 p.m.