Triple
T16228244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USD 388 |
E393910
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Ellis, Kansas |
E403790
|
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: Ellis, Kansas | Statement: [USD 388, locatedIn, Ellis, Kansas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ellis, Kansas Context triple: [USD 388, locatedIn, Ellis, Kansas]
-
A.
Ellis, Kansas
chosen
Ellis, Kansas is a small city in western Kansas known as the boyhood home of automotive pioneer Walter P. Chrysler and for its railroad heritage.
-
B.
Ellsworth, Kansas
Ellsworth, Kansas is a small central Kansas city historically known as a 19th-century cattle town and later as the site of institutions such as St. Joseph Military Academy.
-
C.
Kinsley, Kansas
Kinsley, Kansas is a small city in south-central Kansas known for its location near the geographic midpoint between New York City and San Francisco.
-
D.
Wilsey, Kansas
Wilsey, Kansas is a small rural city located in central Kansas within the Flint Hills region.
-
E.
Willard, Kansas
Willard, Kansas is a small rural city located in Shawnee County in the northeastern part of the state.
- 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_69d87f204df88190a8f88923decf9835 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e23d2785f88190ae80d5d61129d3e5 |
completed | April 17, 2026, 2:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0025f740ec8190ab075c953e27cfba |
completed | May 10, 2026, 6:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.