Triple

T751522
Position Surface form Disambiguated ID Type / Status
Subject Portland International Airport station E15458 entity
Predicate fareZonePolicy P15903 FINISHED
Object standard TriMet fares 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: standard TriMet fares | Statement: [Portland International Airport station, fareZonePolicy, standard TriMet fares]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fareZonePolicy
Context triple: [Portland International Airport station, fareZonePolicy, standard TriMet fares]
  • A. hasFareZone
    Indicates that an entity is located within or associated with a specific fare zone used for pricing or ticketing.
  • B. fareSystem
    Indicates a relationship where a system is used to determine, collect, or manage fares or payments for transportation or similar services.
  • C. farePolicySupport chosen
    Indicates that there is a policy in place governing fares (such as prices, discounts, or rules) that is recognized, enabled, or supported in the given context.
  • D. fareControl
    Indicates that an entity is responsible for monitoring, enforcing, or managing payment of fares for access to a service or facility.
  • E. fareCapping
    Indicates a limit on the total amount a rider can be charged for fares over a set period, after which additional trips are free or discounted.
  • 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_69a493599a0081908da65f3407af1ef2 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a64c67748190aef3522b4b428563 completed March 1, 2026, 8:49 p.m.
PD Predicate disambiguation batch_69a4a501c4cc81908de6d63e3d4f60d7 completed March 1, 2026, 8:43 p.m.
Created at: March 1, 2026, 7:37 p.m.