Triple

T34166771
Position Surface form Disambiguated ID Type / Status
Subject Bedford–Nostrand Avenues station E876432 entity
Predicate fareControlAreaCount P135461 FINISHED
Object multiple 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: multiple | Statement: [Bedford–Nostrand Avenues station, fareControlAreaCount, multiple]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fareControlAreaCount
Context triple: [Bedford–Nostrand Avenues station, fareControlAreaCount, multiple]
  • A. fareControlAreaLocatedIn
    Indicates that a fare control area (e.g., turnstiles or ticket gates) is physically located within a specified larger facility or space.
  • B. hasFareControlAreaCount chosen
    Indicates the number of distinct fare-controlled areas associated with a given transit facility or station.
  • C. fareControlLocation
    Indicates a location where access to or use of a transportation service is regulated, checked, or controlled for fare payment.
  • D. fareControl
    Indicates that an entity is responsible for monitoring, enforcing, or managing payment of fares for access to a service or facility.
  • E. hasControlledAirspace
    Indicates that a specified location or region falls within airspace where aircraft operations are regulated and managed by an aviation authority.
  • 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_69f349ad97ac8190bf1f17417c970e64 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f70fdfb02481908656f80d4f801ddf completed May 3, 2026, 9:05 a.m.
PD Predicate disambiguation batch_69f70f3c5bfc81908585f52e196dafe5 completed May 3, 2026, 9:02 a.m.
Created at: May 1, 2026, 1:54 a.m.