Triple
T8873496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michigan |
E211212
|
entity |
| Predicate | ISO3166-2Code |
P208
|
FINISHED |
| Object | US-MI |
E769368
|
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-MI | Statement: [Michigan, ISO3166-2Code, US-MI]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: US-MI Context triple: [Michigan, ISO3166-2Code, US-MI]
-
A.
US-MI
chosen
US-MI is the ISO 3166-2 subdivision code that uniquely identifies the U.S. state of Michigan.
-
B.
US-ME
US-ME is the ISO 3166-2 code representing the U.S. state of Maine.
-
C.
US-MT
US-MT is the ISO 3166-2 subdivision code that uniquely identifies the U.S. state of Montana.
-
D.
US-MS
US-MS is the ISO 3166-2 code representing the U.S. state of Mississippi.
-
E.
Michigan (most of state)
Michigan (most of state) is the larger portion of the Midwestern U.S. state of Michigan, encompassing its Lower Peninsula and parts of the Upper Peninsula, including major cities like Detroit, Grand Rapids, and Lansing.
- 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_69ca838e78748190934d82db3104f855 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc612952348190856d6964122c3f01 |
completed | April 1, 2026, 12:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfdb8094a88190a88e3f23f9ae17c7 |
completed | April 3, 2026, 3:23 p.m. |
Created at: March 30, 2026, 6:52 p.m.