Triple

T27374101
Position Surface form Disambiguated ID Type / Status
Subject 163rd Street–Amsterdam Avenue E691012 entity
Predicate hasFareControlOn P1973 FINISHED
Object mezzanine level above platforms 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: mezzanine level above platforms | Statement: [163rd Street–Amsterdam Avenue, hasFareControlOn, mezzanine level above platforms]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFareControlOn
Context triple: [163rd Street–Amsterdam Avenue, hasFareControlOn, mezzanine level above platforms]
  • A. hasFareControlLevel
    Indicates the degree or type of access control applied to a transit facility or area for fare payment and validation.
  • B. hasFareControlIntegrationSince
    Indicates that a fare control system has been integrated with another system or entity starting from a specific point in time.
  • C. hasFaregates chosen
    Indicates that an entity is equipped with or contains faregates used to control or validate access, typically for paid entry.
  • D. isWithinFareSystem
    Indicates that one transportation service, route, or area operates under and is covered by a specified fare or ticketing system.
  • E. hasFareZoneSystem
    Indicates that an entity uses or is associated with a particular fare zone system for determining travel costs or ticketing.
  • 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_69ef52022538819081f873d0c84a6dd6 completed April 27, 2026, 12:09 p.m.
NER Named-entity recognition batch_69f6c1265c208190aacd2b551f8f0f82 completed May 3, 2026, 3:29 a.m.
PD Predicate disambiguation batch_69f6bd2415fc81908c23c311aebce66f completed May 3, 2026, 3:12 a.m.
Created at: April 27, 2026, 12:20 p.m.