Triple
T16040242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USD 320 |
E389075
|
entity |
| Predicate | servesCity |
P82
|
FINISHED |
| Object | Wamego, Kansas |
E398596
|
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: Wamego, Kansas | Statement: [USD 320, servesCity, Wamego, Kansas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wamego, Kansas Context triple: [USD 320, servesCity, Wamego, Kansas]
-
A.
Wamego, Kansas
chosen
Wamego, Kansas is a small city in northeastern Kansas known for its agricultural roots, community-focused atmosphere, and attractions like its Oz-themed tourism sites.
-
B.
Mayetta, Kansas
Mayetta, Kansas is a small city in northeastern Kansas that serves as the governmental center of the Prairie Band Potawatomi Nation.
-
C.
Weskan, Kansas
Weskan, Kansas is a small unincorporated rural community located in western Kansas near the Colorado border.
-
D.
Kechi, Kansas
Kechi, Kansas is a small suburban city in south-central Kansas that forms part of the Wichita metropolitan area.
-
E.
Belvue, Kansas
Belvue, Kansas is a small rural city in Pottawatomie County that functions as part of the greater Manhattan, Kansas regional 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1833f84188190baa3a452df880284 |
completed | April 17, 2026, 12:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffe474f89c819086db832b793c15ed |
completed | May 10, 2026, 1:50 a.m. |
Created at: April 10, 2026, 4:56 a.m.