Triple
T3692754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Point Pleasant, Ohio |
E78380
|
entity |
| Predicate | locatedWestOf |
P4239
|
FINISHED |
| Object | Ripley, Ohio |
E315628
|
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: Ripley, Ohio | Statement: [Point Pleasant, Ohio, locatedWestOf, Ripley, Ohio]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ripley, Ohio Context triple: [Point Pleasant, Ohio, locatedWestOf, Ripley, Ohio]
-
A.
Ripley, Ohio
chosen
Ripley, Ohio is a small unincorporated community located in Huron County in the northern part of the state.
-
B.
Wakeman, Ohio
Wakeman, Ohio is a small village in northern Ohio known for its rural character and location within Huron County.
-
C.
New London, Ohio
New London, Ohio is a small village in Huron County known for its rural character and location in north-central Ohio.
-
D.
Ridgefield, Ohio
Ridgefield, Ohio is a small community located in Huron County in the northern part of the U.S. state of Ohio.
-
E.
Riverside, Ohio
Riverside, Ohio is a suburban city in Montgomery County that forms part of the Dayton metropolitan area in southwestern 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_69ad85e285a081908f8cbfa9e2ed9b75 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc4e89f588190951371439a035850 |
completed | March 8, 2026, 6:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bd7f58290881908c7622616a829c75 |
completed | March 20, 2026, 5:09 p.m. |
Created at: March 8, 2026, 3:26 p.m.