Triple
T15985802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Excello, Missouri |
E387689
|
entity |
| Predicate | hasRegionCode |
P3446
|
FINISHED |
| Object | US-MO |
E463440
|
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: US-MO | Statement: [Excello, Missouri, hasRegionCode, US-MO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: US-MO Context triple: [Excello, Missouri, hasRegionCode, US-MO]
-
A.
Missouri and Illinois
Missouri and Illinois are neighboring Midwestern U.S. states whose shared boundary is largely defined by the Mississippi River.
-
B.
MO
MO is the two-letter ISO 3166 country code assigned to the Macao Special Administrative Region of China.
-
C.
MO
chosen
MO is the U.S. Postal Service abbreviation for the state of Missouri.
-
D.
MO
MO is the common abbreviation for Milicja Obywatelska, the state police force that operated in communist Poland from 1944 to 1990.
-
E.
California, Missouri
California, Missouri is a small city in Moniteau County known for its rural Midwestern character and role as a local hub in central Missouri.
- 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_69d86daa562c81908aacc179c0fe8fb5 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e157589d78819091f7b9b1081dd6ad |
completed | April 16, 2026, 9:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffc3cfc8d08190a02abc90c889c8e1 |
completed | May 9, 2026, 11:31 p.m. |
Created at: April 10, 2026, 4:54 a.m.