Triple
T21373949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brooklyn, Ohio |
E527143
|
entity |
| Predicate | borders |
P224
|
FINISHED |
| Object | Linndale, Ohio |
—
|
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: Linndale, Ohio | Statement: [Brooklyn, Ohio, borders, Linndale, Ohio]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Linndale, Ohio Context triple: [Brooklyn, Ohio, borders, Linndale, Ohio]
-
A.
Linndale, Ohio
chosen
Linndale, Ohio is a tiny village in Cuyahoga County known for its small size, proximity to Cleveland, and historically heavy reliance on traffic enforcement for revenue.
-
B.
Lindsey, Ohio
Lindsey, Ohio is a small rural community located in Sandusky County in northwestern Ohio.
-
C.
Ridgefield, Ohio
Ridgefield, Ohio is a small community located in Huron County in the northern part of the U.S. state of Ohio.
-
D.
Lockbourne, Ohio
Lockbourne, Ohio is a small village in central Ohio that is part of the Columbus metropolitan area.
-
E.
Northfield, Ohio
Northfield, Ohio is a small suburban village in Summit County known for its residential character and proximity to the Cleveland 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_69e0b51e80808190ba5cb05667af02a9 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b0b248508190aebeb671e55198da |
completed | April 22, 2026, 11:27 a.m. |
Created at: April 16, 2026, 5:10 p.m.