Triple

T20796846
Position Surface form Disambiguated ID Type / Status
Subject M train E511932 entity
Predicate boroughConnection P141571 FINISHED
Object connects Queens and Manhattan 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: connects Queens and Manhattan | Statement: [M train, boroughConnection, connects Queens and Manhattan]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: boroughConnection
Context triple: [M train, boroughConnection, connects Queens and Manhattan]
  • A. boroughBoard
    Indicates a governance relationship where a borough-level board oversees, coordinates, or makes decisions affecting entities within that borough.
  • B. isOnPiccadillyLineBranch
    Indicates that something (typically a station or track segment) lies on a branch of the Piccadilly Line rather than on its main central section.
  • C. ropewayConnects
    Indicates that a ropeway (such as a cable car or gondola system) provides a direct transportation connection between two locations.
  • D. servedByOvergroundLine
    Indicates that a location or facility is connected to and receives service from an Overground railway line.
  • E. boroughStreet
    Indicates a relationship where a specific street is located within or belongs to a particular borough.
  • 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_69e0b4cc69f481908e98751e697b9df4 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c2ad6f0481909e0bab7119f10f9c completed April 21, 2026, 12:19 a.m.
PD Predicate disambiguation batch_69e5c0575b1c81908d010223fcd1213e completed April 20, 2026, 5:57 a.m.
PDg Predicate description generation batch_69e5c3cbe5788190b7ace43bfdac2ef6 completed April 20, 2026, 6:12 a.m.
Created at: April 16, 2026, 12:39 p.m.