Triple

T1232852
Position Surface form Disambiguated ID Type / Status
Subject New York Central Railroad E26481 entity
Predicate routeBetween P24772 FINISHED
Object New York City and Chicago 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: New York City and Chicago | Statement: [New York Central Railroad, routeBetween, New York City and Chicago]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: routeBetween
Context triple: [New York Central Railroad, routeBetween, New York City and Chicago]
  • A. routeVia
    Indicates that a connection, path, or communication between two points is established or carried out through an intermediate location, node, or channel.
  • B. nearbyTransit
    Indicates that one location has public transportation options situated within a short distance or easy access from it.
  • C. commutesBetween
    Indicates a regular pattern of travel back and forth between two locations, typically for work, study, or routine activities.
  • D. significantlyShortensRouteBetween
    Indicates that one entity provides a connection between two others that makes the path or travel distance between them substantially shorter than alternative routes.
  • E. routeDescription
    Indicates a textual explanation or summary of the path, course, or itinerary taken between locations.
  • 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_69a4948571c88190a9191e451e6035fd completed March 1, 2026, 7:33 p.m.
NER Named-entity recognition batch_69a4be5b40208190b115a6a344402caf completed March 1, 2026, 10:31 p.m.
PD Predicate disambiguation batch_69a4bb65d61c8190bf0424ea0019a98b completed March 1, 2026, 10:19 p.m.
PDg Predicate description generation batch_69a4bbf83584819088c69366f58586cc completed March 1, 2026, 10:21 p.m.
Created at: March 1, 2026, 7:47 p.m.