Triple
T16911838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Decatur |
E410215
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Decatur, Illinois |
E74587
|
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: Decatur, Illinois | Statement: [Lake Decatur, locatedNear, Decatur, Illinois]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Decatur, Illinois Context triple: [Lake Decatur, locatedNear, Decatur, Illinois]
-
A.
Decatur, Illinois
chosen
Decatur, Illinois is a mid-sized industrial and agricultural city in central Illinois known historically for manufacturing, agribusiness, and its location along Lake Decatur.
-
B.
Decatur
Decatur is a historic, densely populated small city in DeKalb County, Georgia, known for its walkable downtown, vibrant arts and dining scene, and close proximity to Atlanta.
-
C.
Decatur
Decatur is a surname of English origin borne by various notable individuals and families.
-
D.
Decatur
Decatur is a city in northern Alabama known for its location along the Tennessee River and its role as an industrial and transportation hub.
-
E.
Decatur
Decatur is a small town located within Otsego County in the state of New York, United States.
- 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3ca3d6be88190bca5e1fdf727141b |
completed | April 18, 2026, 6:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00d458902481908f79cd5a9f72f7fd |
completed | May 10, 2026, 6:54 p.m. |
Created at: April 10, 2026, 5:30 a.m.