Triple

T7791271
Position Surface form Disambiguated ID Type / Status
Subject Fairmount Line E180183 entity
Predicate historicalRouteUsed P12633 FINISHED
Object former New York and New England Railroad main line 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: former New York and New England Railroad main line | Statement: [Fairmount Line, historicalRouteUsed, former New York and New England Railroad main line]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalRouteUsed
Context triple: [Fairmount Line, historicalRouteUsed, former New York and New England Railroad main line]
  • A. hasHistoricalRoute chosen
    Indicates that an entity possesses or is associated with a route that has historical significance or origin.
  • B. historicRoute
    Indicates that a route has historical significance, typically due to its age, past usage, or role in notable events.
  • C. hasTourHistory
    Indicates that an entity has a record of past tours or tour-related activities.
  • D. historicalPass
    Indicates that an entity has successfully completed or passed a historical event, period, or examination related to history.
  • E. hasTransportHistoryAs
    Indicates that an entity has a record or log of being transported, characterized or classified in a specific way.
  • 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_69ca827d22208190b4dc5aa680edcf5d completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69caf78a6d88819093f83528fe88b182 completed March 30, 2026, 10:22 p.m.
PD Predicate disambiguation batch_69cae9111b2481909684a2d4aa4831c2 completed March 30, 2026, 9:20 p.m.
Created at: March 30, 2026, 4:30 p.m.