Triple

T10905583
Position Surface form Disambiguated ID Type / Status
Subject Metrolink fare zones E257559 entity
Predicate fareCalculationRule P49336 FINISHED
Object fare depends on highest and lowest zones travelled through 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: fare depends on highest and lowest zones travelled through | Statement: [Metrolink fare zones, fareCalculationRule, fare depends on highest and lowest zones travelled through]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fareCalculationRule
Context triple: [Metrolink fare zones, fareCalculationRule, fare depends on highest and lowest zones travelled through]
  • A. fareCalculation
    Indicates the process or method used to determine the monetary cost of a trip or service based on specified pricing rules and conditions.
  • B. fareBasis
    Indicates the specific fare rule or pricing category that applies to a ticket or travel segment.
  • C. fareStructure
    Indicates the pricing scheme or set of rules that determine how fares are calculated and applied for a given service or trip.
  • D. fareAppliesTo
    Indicates that a specific fare is applicable to a particular trip, service, passenger category, or travel condition.
  • E. fareStructureFeature chosen
    Indicates a characteristic or condition of how fares are structured, calculated, or applied within a pricing or ticketing system.
  • 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_69d6aa8550c8819095508a2ed9acf3db completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d770656c288190828e71600bb0acd4 completed April 9, 2026, 9:24 a.m.
PD Predicate disambiguation batch_69d70d3d69e08190bb369e9a7927142c completed April 9, 2026, 2:21 a.m.
Created at: April 8, 2026, 9:22 p.m.