Triple

T21440225
Position Surface form Disambiguated ID Type / Status
Subject Zone 18 (NJ Transit) E528918 entity
Predicate fareDetermines P27911 FINISHED
Object price of tickets between Zone 18 and other fare zones 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: price of tickets between Zone 18 and other fare zones | Statement: [Zone 18 (NJ Transit), fareDetermines, price of tickets between Zone 18 and other fare zones]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fareDetermines
Context triple: [Zone 18 (NJ Transit), fareDetermines, price of tickets between Zone 18 and other fare zones]
  • 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. fare
    Indicates the price or cost required for a person or thing to be transported by a particular mode of travel or service.
  • C. fareBasis
    Indicates the specific fare rule or pricing category that applies to a ticket or travel segment.
  • D. fareContext
    Indicates the pricing or fare-related conditions under which a transaction, service, or travel arrangement is applied.
  • E. fareModel
    Indicates a pricing relationship where a specific fare structure, rule set, or calculation method is applied to determine the cost of a trip 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_69e0c4569fa081908101baa24f8745db completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69e8b700237c8190bbcb4bedc4242719 completed April 22, 2026, 11:54 a.m.
PD Predicate disambiguation batch_69e61639ee288190889ffd500d1260f6 completed April 20, 2026, 12:04 p.m.
Created at: April 16, 2026, 6:05 p.m.