Triple
T8338115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lane County, Kansas |
E195839
|
entity |
| Predicate | hasCity |
P316
|
FINISHED |
| Object | Dighton, Kansas |
E728295
|
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: Dighton, Kansas | Statement: [Lane County, Kansas, hasCity, Dighton, Kansas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dighton, Kansas Context triple: [Lane County, Kansas, hasCity, Dighton, Kansas]
-
A.
Dighton, Kansas
chosen
Dighton, Kansas is a small rural city in western Kansas that serves as the administrative and commercial center of Lane County.
-
B.
Dwight, Kansas
Dwight, Kansas is a small rural city in Morris County that forms part of the Manhattan, Kansas metropolitan region.
-
C.
Dorrance, Kansas
Dorrance, Kansas is a small rural city in central Kansas known for its agricultural surroundings and location within Russell County.
-
D.
Alta Vista, Kansas
Alta Vista, Kansas is a small rural city in eastern Kansas that functions as part of the broader Manhattan-area community.
-
E.
Redfield, Kansas
Redfield, Kansas is a small rural city located in southeastern Kansas within Bourbon County.
- 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_69ca82ecbdc481908a55cad8ca062d88 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7fd68e348190a7cb8639a263b50f |
completed | March 31, 2026, 8:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce028586788190b07c601e521eb531 |
completed | April 2, 2026, 5:45 a.m. |
Created at: March 30, 2026, 5:57 p.m.