Triple
T9696157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Celeryville, Ohio |
E234657
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Willard, Ohio |
E294107
|
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: Willard, Ohio | Statement: [Celeryville, Ohio, locatedNear, Willard, Ohio]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Willard, Ohio Context triple: [Celeryville, Ohio, locatedNear, Willard, Ohio]
-
A.
Willard, Ohio
chosen
Willard, Ohio is a small city in north-central Ohio known historically as a railroad town and for its agricultural and manufacturing industries.
-
B.
Waverly, Ohio
Waverly, Ohio is a small city in southern Ohio known as the hometown of the country rock band Pure Prairie League.
-
C.
Whitehouse, Ohio
Whitehouse, Ohio is a small village in northwest Ohio known for its suburban-rural character and proximity to the city of Toledo.
-
D.
Wilmington, Ohio
Wilmington, Ohio is a small city in southwestern Ohio known historically as a regional transportation hub and home to a major air park and agricultural community.
-
E.
Townsend, Ohio
Townsend, Ohio is an unincorporated rural community located in Huron County in northern Ohio.
- 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_69ca84cb580c8190a7e5f4b3bcdaf2a4 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d3a88788190a4235a1ab33341ec |
completed | April 1, 2026, 10:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d380c81c7c81908361d237d79f1ff0 |
completed | April 6, 2026, 9:45 a.m. |
Created at: March 30, 2026, 8:17 p.m.