Triple
T21584397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akron City Hall |
E532610
|
entity |
| Predicate | governs |
P760
|
FINISHED |
| Object | City of Akron |
—
|
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: City of Akron | Statement: [Akron City Hall, governs, City of Akron]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: City of Akron Context triple: [Akron City Hall, governs, City of Akron]
-
A.
Akron, Pennsylvania
Akron, Pennsylvania is a small borough in Lancaster County known for its residential community character and proximity to the region’s agricultural and Amish areas.
-
B.
City of Lorain
The City of Lorain is an industrial and port city on Lake Erie in northern Ohio, known for its steelmaking history and diverse waterfront community.
-
C.
Lithopolis, Ohio
Lithopolis, Ohio is a small village in central Ohio known for its historic charm and annual Honeyfest, located southeast of Columbus.
-
D.
Akron
chosen
Akron is an industrial city in northeastern Ohio known historically for its rubber and tire manufacturing industry.
-
E.
Akron, Michigan
Akron, Michigan is a small rural village located in Tuscola County in the Thumb region of the U.S. state of Michigan.
- 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_69e0c4618bec8190bcb0feb74568cbb1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeeb5f2cc0819095552de70eb2ad8d |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 16, 2026, 6:31 p.m.