Triple
T12255924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sherman Township, Michigan |
E292099
|
entity |
| Predicate | stateCode |
P20781
|
FINISHED |
| Object | MI |
E281766
|
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: MI | Statement: [Sherman Township, Michigan, stateCode, MI]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MI Context triple: [Sherman Township, Michigan, stateCode, MI]
-
A.
MI
chosen
MI is the official two-letter United States Postal Service abbreviation for the state of Michigan.
-
B.
MI
MI is the commonly used abbreviation for the Mumbai Indians, a prominent franchise cricket team in the Indian Premier League.
-
C.
Mi
Mi was the ancestral clan name of the royal house of the ancient Chinese state of Chu, to which King Zhuang of Chu belonged.
-
D.
Mi
Mi is a sub-brand of Xiaomi used primarily for its line of consumer electronics and smart devices, including smartphones, TVs, and streaming boxes.
-
E.
Mil
Mil is a Russian surname most famously associated with Mikhail Mil, the pioneering Soviet aerospace engineer and helicopter designer.
- 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91cc9dd5081908880061d52351850 |
completed | April 10, 2026, 3:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f60abdc5988190a19104385f54fb06 |
completed | May 2, 2026, 2:31 p.m. |
Created at: April 8, 2026, 9:52 p.m.