Triple
T22246656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mound City, Kansas |
E549860
|
entity |
| Predicate | hasOfficialName |
P66
|
FINISHED |
| Object | Mound City, Kansas |
—
|
NE NERFINISHED |
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: Mound City, Kansas | Statement: [Mound City, Kansas, hasOfficialName, Mound City, Kansas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mound City, Kansas Context triple: [Mound City, Kansas, hasOfficialName, Mound City, Kansas]
-
A.
Mound City, Kansas
chosen
Mound City, Kansas is a small rural city in Linn County that serves as the county seat in southeastern Kansas.
-
B.
Mound City, Missouri
Mound City, Missouri is a small city in northwest Missouri that serves as the largest community and a local hub within Holt County.
-
C.
Tecumseh, Kansas
Tecumseh, Kansas is a small unincorporated community in northeastern Kansas, located just east of Topeka along the Kansas River.
-
D.
McPherson, Kansas
McPherson, Kansas is a small central Kansas city known for its manufacturing base, historic downtown, and role as a regional educational and cultural hub.
-
E.
Mound Valley, Kansas
Mound Valley, Kansas is a small rural city located in southeastern Kansas within Labette County.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e41d9408190bd770cf282e22753 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f13218d1f88190b64b7f301328fa98 |
completed | April 28, 2026, 10:18 p.m. |
Created at: April 16, 2026, 8:38 p.m.