Triple
T11523204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neosho River |
E273218
|
entity |
| Predicate | flowsThrough |
P225
|
FINISHED |
| Object | Parsons, Kansas |
E568349
|
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: Parsons, Kansas | Statement: [Neosho River, flowsThrough, Parsons, Kansas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Parsons, Kansas Context triple: [Neosho River, flowsThrough, Parsons, Kansas]
-
A.
Parsons, Kansas
chosen
Parsons, Kansas is a small city in Labette County known historically as a regional railroad hub and industrial center in southeastern Kansas.
-
B.
Peabody, Kansas
Peabody, Kansas is a small historic city in central Kansas known for its 19th-century architecture and annual Independence Day celebrations.
-
C.
Park, Kansas
Park, Kansas is a small rural city located in Gove County in western Kansas, known for its agricultural surroundings and tight-knit community.
-
D.
Newton, Kansas
Newton, Kansas is a small city in south-central Kansas known historically as a railroad hub and gateway to the American West.
-
E.
St. Paul, Kansas
St. Paul, Kansas is a small rural city in southeastern Kansas known for its strong Catholic heritage and historic mission roots.
- 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_69d6aae3fbec8190a14632a5df2538b6 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d87fd26648819083de19bcddf8ad69 |
completed | April 10, 2026, 4:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6717a5ca081908bdba9b944b76258 |
completed | May 2, 2026, 9:49 p.m. |
Created at: April 8, 2026, 9:37 p.m.