Triple
T10834961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Douglas County, Kansas |
E255728
|
entity |
| Predicate | hasTown |
P847
|
FINISHED |
| Object | Lecompton, Kansas |
E908251
|
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: Lecompton, Kansas | Statement: [Douglas County, Kansas, hasTown, Lecompton, Kansas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lecompton, Kansas Context triple: [Douglas County, Kansas, hasTown, Lecompton, Kansas]
-
A.
Lecompton, Kansas
chosen
Lecompton, Kansas is a small historic town in northeastern Kansas that served as the territorial capital during the 1850s and played a key role in the events leading up to the American Civil War.
-
B.
Lewis, Kansas
Lewis, Kansas is a small rural city located in Edwards County in south-central Kansas, United States.
-
C.
Wilson, Kansas
Wilson, Kansas is a small rural city in central Kansas known for its Czech heritage and location near Wilson Lake.
-
D.
Eudora, Kansas
Eudora, Kansas is a small city in northeastern Kansas located between Lawrence and the Kansas City metropolitan area.
-
E.
Tecumseh, Kansas
Tecumseh, Kansas is a small unincorporated community in northeastern Kansas, located just east of Topeka along the Kansas River.
- 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d74425447081908fb51c7edf54af67 |
completed | April 9, 2026, 6:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e4acb7fdac8190bced7e26c948ee4a |
completed | April 19, 2026, 10:21 a.m. |
Created at: April 8, 2026, 9:19 p.m.