Triple

T11698710
Position Surface form Disambiguated ID Type / Status
Subject Chicago South Shore and South Bend Railroad E278064 entity
Predicate beganThroughServiceBetweenChicagoAndSouthBend P101317 FINISHED
Object 1909 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: 1909 | Statement: [Chicago South Shore and South Bend Railroad, beganThroughServiceBetweenChicagoAndSouthBend, 1909]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: beganThroughServiceBetweenChicagoAndSouthBend
Context triple: [Chicago South Shore and South Bend Railroad, beganThroughServiceBetweenChicagoAndSouthBend, 1909]
  • A. distanceFromChicagoTerminus
    Indicates the measured distance of an entity from the Chicago terminus point along a specified route or network.
  • B. distanceToSouthBend
    Indicates the measured or calculated distance between a given entity and the location South Bend.
  • C. blueLineServiceBegan
    Indicates that service on the Blue Line began operating at a specified time or event.
  • D. distanceFromChicagoUnionStation
    Indicates the measured distance between a given location and Chicago Union Station.
  • E. enteredConrailOn
    Indicates that an entity began employment with, or formally joined, Conrail on a specified date or at a specified time.
  • 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_69d6aafe02d881909900d54ad7d4af84 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a47df68c81908a91919a69b4880d completed April 10, 2026, 7:19 a.m.
PD Predicate disambiguation batch_69d88a7b30948190b616a9db5c5488d5 completed April 10, 2026, 5:28 a.m.
PDg Predicate description generation batch_69d89546a8688190b51455b5e12caf91 completed April 10, 2026, 6:14 a.m.
Created at: April 8, 2026, 9:40 p.m.