Triple
T20522952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jewel of the Port |
E503856
|
entity |
| Predicate | city |
P40
|
FINISHED |
| Object | Lorain |
—
|
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: Lorain | Statement: [Jewel of the Port, city, Lorain]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lorain Context triple: [Jewel of the Port, city, Lorain]
-
A.
Lorain
chosen
Lorain is an industrial city on Lake Erie in northern Ohio, historically known for its steel production and shipbuilding.
-
B.
Youngstown
Youngstown is an industrial city in northeastern Ohio historically known for its steel production and central role in the Rust Belt’s economic rise and decline.
-
C.
Akron
Akron is an industrial city in northeastern Ohio known historically for its rubber and tire manufacturing industry.
-
D.
Cleves
Cleves is a historic town in western Germany near the Dutch border, known for its medieval castle and role as a former ducal capital in the Lower Rhine region.
-
E.
Johnstown, Ohio
Johnstown, Ohio is a small village in central Ohio known for its close-knit community and location within the Columbus metropolitan area.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4b3a6e08190ae663701f50fab8e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69f471f18819091e8a57161fe0225 |
completed | April 20, 2026, 9:48 p.m. |
Created at: April 16, 2026, 11:36 a.m.