Triple
T6061920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northeastern Missouri |
E135051
|
entity |
| Predicate | hasCity |
P316
|
FINISHED |
| Object | Shelbina, Missouri |
E533027
|
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: Shelbina, Missouri | Statement: [Northeastern Missouri, hasCity, Shelbina, Missouri]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shelbina, Missouri Context triple: [Northeastern Missouri, hasCity, Shelbina, Missouri]
-
A.
Shelbina, Missouri
chosen
Shelbina, Missouri is a small city in northeastern Missouri that serves as an important local hub for government, services, and commerce in Shelby County.
-
B.
Sheldon, Missouri
Sheldon, Missouri is a small rural city located in southwestern Missouri within Vernon County.
-
C.
Sibley, Missouri
Sibley, Missouri is a small village in western Missouri known for its proximity to the historic Fort Osage site along the Missouri River.
-
D.
Shelbyville, Missouri
Shelbyville, Missouri is a small city in northeastern Missouri that serves as the county seat and local hub for Shelby County.
-
E.
Bellamy, Missouri
Bellamy, Missouri is a small unincorporated community located in rural Vernon County in the western 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_69c00878d06881909ee78e88913bf890 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0572100e8819084c3174921a2d527 |
completed | March 22, 2026, 8:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c669d473388190a6e998956dd48e7a |
completed | March 27, 2026, 11:28 a.m. |
Created at: March 22, 2026, 4:10 p.m.