Triple
T18475934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marshall County, Kansas |
E451431
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Frankfort, 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: Frankfort, Kansas | Statement: [Marshall County, Kansas, contains, Frankfort, Kansas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Frankfort, Kansas Context triple: [Marshall County, Kansas, contains, Frankfort, Kansas]
-
A.
Frankfort, Kansas
chosen
Frankfort, Kansas is a small rural city in Marshall County known for its agricultural community and location in northeastern Kansas.
-
B.
Franklin, Kansas
Franklin, Kansas is a small unincorporated community in southeastern Kansas known historically as a coal mining town.
-
C.
Louisville, Kansas
Louisville, Kansas is a small rural community in Pottawatomie County that forms part of the Manhattan, Kansas region.
-
D.
Wellington, Kansas
Wellington, Kansas is a small city in south-central Kansas known historically as a regional agricultural and railroad hub.
-
E.
Hartford, Kansas
Hartford, Kansas is a small rural city in east-central Kansas known for its close-knit community and agricultural surroundings.
- 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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53062f67881909620c4e8fc00eb7d |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 11:34 a.m.