Triple

T31372057
Position Surface form Disambiguated ID Type / Status
Subject RMV zone 5000 E800188 entity
Predicate fareCalculationUse P27911 FINISHED
Object basis for determining ticket price within RMV 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: basis for determining ticket price within RMV | Statement: [RMV zone 5000, fareCalculationUse, basis for determining ticket price within RMV]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fareCalculationUse
Context triple: [RMV zone 5000, fareCalculationUse, basis for determining ticket price within RMV]
  • A. fareCalculation chosen
    Indicates the process or method used to determine the monetary cost of a trip or service based on specified pricing rules and conditions.
  • B. fareContext
    Indicates the pricing or fare-related conditions under which a transaction, service, or travel arrangement is applied.
  • C. fareBasis
    Indicates the specific fare rule or pricing category that applies to a ticket or travel segment.
  • D. fare
    Indicates the price or cost required for a person or thing to be transported by a particular mode of travel or service.
  • E. fareType
    Indicates the category or class of fare (such as standard, discounted, or promotional) that applies to a given trip, ticket, or pricing instance.
  • 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_69f224e6b7448190ac6bf97ad7364160 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f69f8a5d2c81908d4d0d43fc72966f completed May 3, 2026, 1:06 a.m.
PD Predicate disambiguation batch_69f69d1d25e88190a7f57d323574da90 completed May 3, 2026, 12:55 a.m.
Created at: April 29, 2026, 9:18 p.m.