Triple
T11369688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nemaha County, Kansas |
E269308
|
entity |
| Predicate | hasJurisdiction |
P285
|
FINISHED |
| Object | Corning, Kansas |
E931689
|
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: Corning, Kansas | Statement: [Nemaha County, Kansas, hasJurisdiction, Corning, Kansas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Corning, Kansas Context triple: [Nemaha County, Kansas, hasJurisdiction, Corning, Kansas]
-
A.
Kinsley, Kansas
Kinsley, Kansas is a small city in south-central Kansas known for its location near the geographic midpoint between New York City and San Francisco.
-
B.
Oneida, Kansas
chosen
Oneida, Kansas is a small rural city located in Nemaha County in the northeastern part of the state.
-
C.
Langdon, Kansas
Langdon, Kansas is a small rural community located in Reno County in the central part of the U.S. state of Kansas.
-
D.
Schoenchen, Kansas
Schoenchen, Kansas is a small rural city in central Kansas known for its German-Russian heritage and close-knit community.
-
E.
Hudson, Kansas
Hudson, Kansas is a small rural city located in Stafford County in central Kansas, known for its agricultural surroundings and tight-knit community.
- 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_69d6aacca1048190b39dbbc2174616fa |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7ea89e1148190b0ca29db9d7e2cbd |
completed | April 9, 2026, 6:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f12fa07fc081909a42f9c19ad38511 |
completed | April 28, 2026, 10:07 p.m. |
Created at: April 8, 2026, 9:33 p.m.