Triple
T21649659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stow |
E534301
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Tallmadge |
—
|
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: Tallmadge | Statement: [Stow, adjacentTo, Tallmadge]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tallmadge Context triple: [Stow, adjacentTo, Tallmadge]
-
A.
Tallmadge
Tallmadge is a small city in northeastern Ohio known for its historic town square and role as a suburb within the Akron metropolitan area.
-
B.
Pomeroy
Pomeroy is a small rural town in KwaZulu-Natal, South Africa, known for its Zulu cultural heritage and agricultural surroundings.
-
C.
Pomeroy
Pomeroy is a surname of English origin that appears as the middle name of the British Army officer George Pomeroy Colley.
-
D.
Pomeroy
Pomeroy is a small village in County Tyrone, Northern Ireland, known for its rural setting and surrounding upland landscapes.
-
E.
Tallmadge, Ohio
chosen
Tallmadge, Ohio is a small city in northeastern Ohio known for its historic New England–style town center and early 19th-century origins.
- 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_69e0c466aec88190ba39c7543dbc8ba2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef5913cd9c81908a6ce9bc741416bf |
completed | April 27, 2026, 12:39 p.m. |
Created at: April 16, 2026, 6:35 p.m.