Triple

T22318847
Position Surface form Disambiguated ID Type / Status
Subject Zone 3 (WMATA fare structure) E551724 entity
Predicate fareZoneRelativePosition P54838 FINISHED
Object outer zone relative to central Washington, D.C. 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: outer zone relative to central Washington, D.C. | Statement: [Zone 3 (WMATA fare structure), fareZoneRelativePosition, outer zone relative to central Washington, D.C.]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fareZoneRelativePosition
Context triple: [Zone 3 (WMATA fare structure), fareZoneRelativePosition, outer zone relative to central Washington, D.C.]
  • A. fareZoneHierarchyPosition chosen
    Indicates the relative level or rank of a fare zone within a hierarchical fare zone structure.
  • B. fareZoneIncludes
    Indicates that a specified fare zone geographically or logically contains a given location, stop, or segment for fare calculation purposes.
  • C. fareZoneDescription
    Indicates the textual description of the fare zone associated with a service, location, or segment.
  • D. adjacentFareZone
    Indicates that two fare zones are directly next to each other, sharing a common boundary without any zones in between.
  • E. fareZoneStart
    Indicates the fare zone in which a journey, ticket, or pricing calculation begins.
  • 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_69e11e4776588190abb21e5cea79973f completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15762fac08190a6a514baffbbbca1 completed April 29, 2026, 12:57 a.m.
PD Predicate disambiguation batch_69e73004d9e88190bb862319a5aea06b completed April 21, 2026, 8:06 a.m.
Created at: April 16, 2026, 8:42 p.m.