Triple
T5547752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shelby County, Missouri |
E145450
|
entity |
| Predicate | hasISO3166-2Code |
P208
|
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: [Shelby County, Missouri, hasISO3166-2Code, US-MO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: US-MO Context triple: [Shelby County, Missouri, hasISO3166-2Code, 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.
E.D. Mo.
E.D. Mo. is the standard legal abbreviation for the United States District Court for the Eastern District of Missouri, a federal trial court within the Eighth Circuit.
-
E.
Northeastern Missouri
Northeastern Missouri is a predominantly rural region of Missouri known for its small towns, agricultural landscape, and location along the Mississippi River.
- 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_69c008fb879c81909f5bfa56fadc1d46 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01fe0244c8190aeb995f79f22a039 |
completed | March 22, 2026, 4:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0282ace308190a714685579f2a789 |
completed | March 22, 2026, 5:34 p.m. |
Created at: March 22, 2026, 3:35 p.m.