Triple

T8400495
Position Surface form Disambiguated ID Type / Status
Subject Guiney Station E198156 entity
Predicate railroadServed P782 FINISHED
Object Richmond, Fredericksburg and Potomac Railroad E198158 NE FINISHED

How this triple was built (3 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: Richmond, Fredericksburg and Potomac Railroad | Statement: [Guiney Station, railroadServed, Richmond, Fredericksburg and Potomac Railroad]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Richmond, Fredericksburg and Potomac Railroad
Context triple: [Guiney Station, railroadServed, Richmond, Fredericksburg and Potomac Railroad]
  • A. Richmond, Fredericksburg and Potomac Railroad chosen
    The Richmond, Fredericksburg and Potomac Railroad was a historic rail line in Virginia that served as a key north–south transportation corridor linking Washington, D.C. with Richmond and points south.
  • B. Alexandria, Loudoun and Hampshire Railroad
    The Alexandria, Loudoun and Hampshire Railroad was a 19th-century Virginia railway line that played a strategic role during the American Civil War, including in early engagements such as the Battle of Vienna.
  • C. Richmond and Petersburg Railroad
    The Richmond and Petersburg Railroad was a 19th-century rail line in Virginia that played a key role in connecting Richmond to southern routes and later became part of larger systems like the Atlantic Coast Line Railroad.
  • D. Washington and Old Dominion Railroad
    The Washington and Old Dominion Railroad was a regional rail line in Northern Virginia that operated from the 19th to the mid-20th century, later converted into the popular Washington & Old Dominion Railroad Trail.
  • E. Virginian Railway
    The Virginian Railway was an early 20th-century American coal-hauling railroad that operated primarily in West Virginia and Virginia, renowned for its efficient, heavy-duty freight operations and later incorporation into the Norfolk and Western Railway.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: railroadServed
Context triple: [Guiney Station, railroadServed, Richmond, Fredericksburg and Potomac Railroad]
  • A. railwayTypeServed
    Indicates the type of railway system or service that a given entity (such as a station, line, or facility) is designed to serve or accommodate.
  • B. servedByRailroad chosen
    Indicates that a location or facility is provided with transportation or service by a railroad line or company.
  • C. servedRailroadsIn
    Indicates that an individual or entity provided service or worked in an official capacity for one or more specified railroad companies.
  • D. servedByRailBranch
    Indicates that a location or facility is connected to and provided service by a specific railway branch line.
  • E. relatedRailroad
    Indicates that there is an association or connection between an entity and a specific railroad, such as ownership, operation, service, or historical linkage.
  • F. None of above.

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_69ca82f816bc8190ab321c07d72208c1 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb824bfcbc8190b26bfcb5f8c4777c completed March 31, 2026, 8:14 a.m.
NED1 Entity disambiguation (via context triple) batch_69ce02e129bc819081e6ea2dd43becba completed April 2, 2026, 5:47 a.m.
PD Predicate disambiguation batch_69cb70d24b248190a326aa6804f942b5 completed March 31, 2026, 6:59 a.m.
Created at: March 30, 2026, 6:04 p.m.