Triple
T3265766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sibley, Missouri |
E68523
|
entity |
| Predicate | stateCode |
P20781
|
FINISHED |
| Object | MO |
E19676
|
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: MO | Statement: [Sibley, Missouri, stateCode, MO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MO Context triple: [Sibley, Missouri, stateCode, MO]
-
A.
MO
MO is the two-letter ISO 3166 country code assigned to the Macao Special Administrative Region of China.
-
B.
MA
MA is the stock ticker symbol for Mastercard Incorporated, a leading global payments and financial services company.
-
C.
MA
MA is the two-letter ISO 3166-1 alpha-2 country code assigned to Morocco.
-
D.
Nevada, Missouri
Nevada, Missouri is a small city in western Missouri that serves as the county seat and regional hub for Vernon County.
-
E.
Missouri
chosen
Missouri is a U.S. state in the Midwest known for its major cities like St. Louis and Kansas City, its role as a historic gateway to the American West, and its diverse mix of agricultural and industrial economies.
- 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_69ad8590444081909e8107a8aeef3a23 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adafcc99908190897230b4b71e2ea8 |
completed | March 8, 2026, 5:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b28eed68c08190994376bfbfeae949 |
completed | March 12, 2026, 10:01 a.m. |
Created at: March 8, 2026, 3:09 p.m.