Triple

T8292555
Position Surface form Disambiguated ID Type / Status
Subject MBTA Commuter Rail fare zones E193934 entity
Predicate zoneAssignmentCriterion P82575 FINISHED
Object distance from Boston terminals 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: distance from Boston terminals | Statement: [MBTA Commuter Rail fare zones, zoneAssignmentCriterion, distance from Boston terminals]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: zoneAssignmentCriterion
Context triple: [MBTA Commuter Rail fare zones, zoneAssignmentCriterion, distance from Boston terminals]
  • A. zone
    Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
  • B. zoneType
    Indicates the classification or category of a zone that specifies its type or functional designation.
  • C. zoneConcept
    Indicates that one entity is associated with, defined by, or operates within a particular zone or conceptual area specified by another entity.
  • D. zoningRole
    Indicates the specific function, restriction, or regulatory status assigned to a property or area under zoning regulations.
  • E. regionQualifier
    Indicates that one entity specifies or constrains the regional or geographic scope applicable to another entity.
  • F. None of above. chosen

Provenance (4 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_69ca82e32db481908b72f3804fa71152 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb7c9ccbfc81908825685c23b80d23 completed March 31, 2026, 7:49 a.m.
PD Predicate disambiguation batch_69cb70b5b5348190b296e0ecec95de60 completed March 31, 2026, 6:59 a.m.
PDg Predicate description generation batch_69cb76d648988190ab0669cc0592e827 completed March 31, 2026, 7:25 a.m.
Created at: March 30, 2026, 5:52 p.m.