Triple

T25386515
Position Surface form Disambiguated ID Type / Status
Subject Myki Zone 2 E631538 entity
Predicate fareStructureRelation P49336 FINISHED
Object outer zone in Melbourne’s Myki fare structure 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: outer zone in Melbourne’s Myki fare structure | Statement: [Myki Zone 2, fareStructureRelation, outer zone in Melbourne’s Myki fare structure]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fareStructureRelation
Context triple: [Myki Zone 2, fareStructureRelation, outer zone in Melbourne’s Myki fare structure]
  • A. fareStructure
    Indicates the pricing scheme or set of rules that determine how fares are calculated and applied for a given service or trip.
  • B. fareStructureFeature chosen
    Indicates a characteristic or condition of how fares are structured, calculated, or applied within a pricing or ticketing system.
  • C. fareZoneRelation
    Indicates a relationship between a location or service and a specific fare zone used for pricing or ticketing.
  • D. fareBasis
    Indicates the specific fare rule or pricing category that applies to a ticket or travel segment.
  • E. farePolicyRelatedTo
    Indicates a relationship where a fare policy is associated with, applies to, or governs a particular entity, context, or service.
  • 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_69e75a8c50788190aabaa9f96710fc43 completed April 21, 2026, 11:07 a.m.
NER Named-entity recognition batch_69f5656a1e8081908dbec5e5e1d21319 completed May 2, 2026, 2:46 a.m.
PD Predicate disambiguation batch_69f45d0dbc8c8190beecce679fce90a4 completed May 1, 2026, 7:58 a.m.
Created at: April 21, 2026, 1:47 p.m.