Triple

T30373040
Position Surface form Disambiguated ID Type / Status
Subject Sheridan Square E772601 entity
Predicate subwayLineServedByNearbyStation P18378 FINISHED
Object IRT Broadway–Seventh Avenue Line NE NERFINISHED

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: IRT Broadway–Seventh Avenue Line | Statement: [Sheridan Square, subwayLineServedByNearbyStation, IRT Broadway–Seventh Avenue Line]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: subwayLineServedByNearbyStation
Context triple: [Sheridan Square, subwayLineServedByNearbyStation, IRT Broadway–Seventh Avenue Line]
  • A. subwayLine chosen
    Indicates that there is a subway line connection or service relationship between the referenced entities.
  • B. subwayStation
    Indicates that one entity is a subway station associated with, located in, or serving the other entity.
  • C. nearbyMainlineConnection
    Indicates that one entity has a mainline connection located in close physical proximity to another entity.
  • D. adjacentStationOnMetropolitanLine
    Indicates that one station is directly next to another station along the Metropolitan Line, with no other stations in between on that line.
  • E. subwayStationsApprox
    Indicates that one subway station is approximately located near or corresponds to another subway station, allowing for minor differences in position or naming.
  • 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_69f2248d71408190aec0d5c2001b1cff completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f6828532d081909897bbe49b280ced completed May 2, 2026, 11:02 p.m.
PD Predicate disambiguation batch_69f678d019fc8190913662cd2f87b857 completed May 2, 2026, 10:21 p.m.
Created at: April 29, 2026, 7:59 p.m.