Triple

T16723743
Position Surface form Disambiguated ID Type / Status
Subject Erie federal courthouse E406414 entity
Predicate locatedInJurisdiction P40 FINISHED
Object City of Erie E194483 NE 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: City of Erie | Statement: [Erie federal courthouse, locatedInJurisdiction, City of Erie]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: City of Erie
Context triple: [Erie federal courthouse, locatedInJurisdiction, City of Erie]
  • A. Erie, Pennsylvania chosen
    Erie, Pennsylvania is a mid-sized industrial and port city in northwestern Pennsylvania on the shores of Lake Erie, known for its manufacturing history and lakefront tourism.
  • B. ERIE
    ERIE is the station code for Erie station on Philadelphia’s Broad Street Line subway system.
  • C. Johnstown, Ohio
    Johnstown, Ohio is a small village in central Ohio known for its close-knit community and location within the Columbus metropolitan area.
  • D. Lorain
    Lorain is an industrial city on Lake Erie in northern Ohio, historically known for its steel production and shipbuilding.
  • E. Johnstown
    Johnstown is a small community in eastern Ontario, Canada, located along the St. Lawrence River near the Canada–U.S. border.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d8838f242881908abd8bc138795886 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e38745d2048190b476e5aa83ec7fec completed April 18, 2026, 1:29 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00c29693dc819096993d8ba0fb3d71 completed May 10, 2026, 5:38 p.m.
Created at: April 10, 2026, 5:20 a.m.