Triple
T13074107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elkhart County, Indiana |
E329527
|
entity |
| Predicate | hasCountySeat |
P383
|
FINISHED |
| Object | Goshen, Indiana |
E683963
|
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: Goshen, Indiana | Statement: [Elkhart County, Indiana, hasCountySeat, Goshen, Indiana]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Goshen, Indiana Context triple: [Elkhart County, Indiana, hasCountySeat, Goshen, Indiana]
-
A.
Goshen, Indiana, United States
Goshen, Indiana, United States is a small Midwestern city known as the county seat of Elkhart County and for its manufacturing and agricultural industries.
-
B.
Greensburg, Indiana
Greensburg, Indiana is a small Midwestern city known for its historic courthouse square and the famous tree growing from the Decatur County Courthouse tower.
-
C.
Goshen
Goshen is a small town in Utah County, Utah, situated in the southern part of Utah Valley.
-
D.
Goshen
chosen
Goshen is a small city in northern Indiana known for its manufacturing base, Mennonite and Amish heritage, and historic downtown.
-
E.
Goshen
Goshen was a short-lived Boer republic in southern Africa established by Voortrekker settlers during the 1880s.
- 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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d981160e388190bab942a2ded2903e |
completed | April 10, 2026, 11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6d606ac6481908d18a288d5eed472 |
completed | May 3, 2026, 4:58 a.m. |
Created at: April 9, 2026, 9 p.m.