Triple
T23005458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Readsville, Missouri |
E572753
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Steedman, Missouri |
—
|
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: Steedman, Missouri | Statement: [Readsville, Missouri, locatedNear, Steedman, Missouri]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Steedman, Missouri Context triple: [Readsville, Missouri, locatedNear, Steedman, Missouri]
-
A.
Steedman, Missouri
chosen
Steedman, Missouri is a small unincorporated rural community located in Callaway County in the U.S. state of Missouri.
-
B.
Estill, Missouri
Estill, Missouri is a small unincorporated community located in Howard County in the central part of the state.
-
C.
Stanberry, Missouri
Stanberry, Missouri is a small rural city in northwest Missouri that serves as a local community and service center within Gentry County.
-
D.
Stet, Missouri
Stet, Missouri is a small unincorporated rural community located in Ray County in the U.S. state of Missouri.
-
E.
Stet, Missouri
Stet, Missouri is a small unincorporated rural community located in Carroll County in the U.S. state of Missouri.
- 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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18356417881908c8d6ee56bdc85f5 |
completed | April 29, 2026, 4:04 a.m. |
Created at: April 17, 2026, 3:51 p.m.