Triple
T21937468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dymond |
E541729
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Coleman Township |
—
|
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: Coleman Township | Statement: [Dymond, adjacentTo, Coleman Township]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Coleman Township Context triple: [Dymond, adjacentTo, Coleman Township]
-
A.
Coleman Township
chosen
Coleman Township is a small rural municipality located within Ontario's Timiskaming District in Canada.
-
B.
Courtland Township
Courtland Township is a civil township located in Kent County in the U.S. state of Michigan.
-
C.
Casey Township
Casey Township is a small rural municipality located within Ontario’s Timiskaming District in Canada.
-
D.
Logan Township
Logan Township is a suburban municipality in Gloucester County, New Jersey, known for its mix of residential neighborhoods, industrial parks, and proximity to major transportation routes.
-
E.
Bowne Township
Bowne Township is a civil township located in Kent County in 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_69e0c47e2e5c81909a7f74ce3de50911 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1241e35bc81909eb3225d5cd97b92 |
completed | April 28, 2026, 9:18 p.m. |
Created at: April 16, 2026, 7:55 p.m.