Triple

T7118206
Position Surface form Disambiguated ID Type / Status
Subject Southern Cross railway station E165872 entity
Predicate fareSystem P395 FINISHED
Object Myki E158348 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: Myki | Statement: [Southern Cross railway station, fareSystem, Myki]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Myki
Context triple: [Southern Cross railway station, fareSystem, Myki]
  • A. Myki chosen
    Myki is Melbourne’s contactless smartcard public transport ticketing system used across trains, trams, and buses in Victoria, Australia.
  • B. Myki Pass
    Myki Pass is a prepaid, time-based public transport ticket used for unlimited travel within selected zones on Victoria’s Myki system.
  • C. Opal card
    The Opal card is a reusable, contactless smartcard used to pay for public transport across much of New South Wales, Australia.
  • D. ORCA card
    The ORCA card is a reusable, contactless smart card used to pay fares across multiple public transit systems in the Puget Sound region of Washington State.
  • E. 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.
  • 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_69c6888227bc8190a1394679e3116f90 completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e618bdac8190be291468b7d977bb completed March 27, 2026, 8:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7bf7c0bb88190ac03e2279512d837 completed March 28, 2026, 11:46 a.m.
Created at: March 27, 2026, 2:43 p.m.