Triple
T21995241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missouri Route 6 |
E543187
|
entity |
| Predicate | passesThrough |
P225
|
FINISHED |
| Object | La Belle, 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: La Belle, Missouri | Statement: [Missouri Route 6, passesThrough, La Belle, Missouri]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: La Belle, Missouri Context triple: [Missouri Route 6, passesThrough, La Belle, Missouri]
-
A.
La Belle, Missouri
chosen
La Belle, Missouri is a small rural community located in northeastern Missouri within Lewis County.
-
B.
Bellamy, Missouri
Bellamy, Missouri is a small unincorporated community located in rural Vernon County in the western part of the state.
-
C.
Brunot, Missouri
Brunot, Missouri is an unincorporated rural community located in Wayne County in southeastern Missouri.
-
D.
Bevier, Missouri
Bevier, Missouri is a small city located in north-central Missouri that is part of the Macon County region.
-
E.
Van Buren, Missouri
Van Buren, Missouri is a small town in the Ozarks that serves as a popular gateway for outdoor recreation along the Current and Jacks Fork rivers.
- 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_69e11e2c814c8190837d072789000486 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1276493bc81908567445e901bc3a7 |
completed | April 28, 2026, 9:32 p.m. |
Created at: April 16, 2026, 8:19 p.m.