Triple
T13655742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Erie |
E326855
|
entity |
| Predicate | governingBody |
P46
|
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: [Port of Erie, governingBody, City of Erie]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: City of Erie Context triple: [Port of Erie, governingBody, 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.
Lorain
Lorain is an industrial city on Lake Erie in northern Ohio, historically known for its steel production and shipbuilding.
-
D.
Johnstown
Johnstown is a small community in eastern Ontario, Canada, located along the St. Lawrence River near the Canada–U.S. border.
-
E.
Johnstown
Johnstown is a small historic city in Fulton County, New York, known for its colonial-era roots and role in the Mohawk Valley region.
- 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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc61d56e4819084ae3c16ecdf4a05 |
completed | April 12, 2026, 4:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f79d46c48c81908d64f1a32cf08c5b |
completed | May 3, 2026, 7:08 p.m. |
Created at: April 9, 2026, 9:52 p.m.