Triple
T21321127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Havensville, Kansas |
E525617
|
entity |
| Predicate | hasOfficialName |
P66
|
FINISHED |
| Object | Havensville, 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: Havensville, Kansas | Statement: [Havensville, Kansas, hasOfficialName, Havensville, Kansas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Havensville, Kansas Context triple: [Havensville, Kansas, hasOfficialName, Havensville, Kansas]
-
A.
Havensville, Kansas
chosen
Havensville, Kansas is a small rural city in Pottawatomie County in northeastern Kansas.
-
B.
Haven, Kansas
Haven, Kansas is a small rural city in south-central Kansas known for its agricultural community and location within Reno County.
-
C.
Hiattville, Kansas
Hiattville, Kansas is a small unincorporated rural community located in southeastern Kansas.
-
D.
Harveyville, Kansas
Harveyville, Kansas is a small rural town in eastern Kansas known for its tight-knit community and location within the Flint Hills region.
-
E.
Hanston, Kansas
Hanston, Kansas is a small rural city located in southwestern Kansas within Hodgeman 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_69e0b51ad810819098c12392c8e55f6c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e77ed1538c8190954da114e49dfa36 |
completed | April 21, 2026, 1:42 p.m. |
Created at: April 16, 2026, 4:39 p.m.