Triple

T35231227
Position Surface form Disambiguated ID Type / Status
Subject Connecticut Southern Railroad E1017238 entity
Predicate operatesFreightServiceInCity P152995 FINISHED
Object Hartford, Connecticut NE NERFINISHED

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: Hartford, Connecticut | Statement: [Connecticut Southern Railroad, operatesFreightServiceInCity, Hartford, Connecticut]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: operatesFreightServiceInCity
Context triple: [Connecticut Southern Railroad, operatesFreightServiceInCity, Hartford, Connecticut]
  • A. operatedFreightServiceIn chosen
    Indicates that an entity operated a freight transportation service within or across the specified geographic area or route.
  • B. servesAsCargoHubFor
    Indicates that one entity functions as a central location or facility for handling, consolidating, and distributing cargo associated with another entity.
  • C. operatesBetweenCity
    Indicates a transportation or service route that runs between two cities.
  • D. freightConnections
    Indicates the existence or characteristics of transportation links used to move freight or cargo between locations or entities.
  • E. operatedFreightInterchangeWith
    Indicates that one entity operated a freight interchange service or facility jointly with another entity, enabling the transfer of freight between their respective operations.
  • 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_69f76de12e4c8190bc46b71a32858356 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_6a01289f781481908f3788f8a719f2f4 completed May 11, 2026, 12:53 a.m.
PD Predicate disambiguation batch_6a012823c7248190961e20be48dd6246 completed May 11, 2026, 12:51 a.m.
Created at: May 3, 2026, 4:02 p.m.