Triple
T30034777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michigander |
E763123
|
entity |
| Predicate | hasAssociatedStateAbbreviation |
P2461
|
FINISHED |
| Object | MI |
—
|
NE NERFINISHED |
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: [Michigander, hasAssociatedStateAbbreviation, MI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedStateAbbreviation Context triple: [Michigander, hasAssociatedStateAbbreviation, MI]
-
A.
hasPostalAbbreviationState
chosen
Indicates that a state is associated with a specific standardized postal abbreviation.
-
B.
associatedWithStateCode
Indicates that an entity has a connection or linkage to a particular state identified by its state code.
-
C.
associatedWithUSStateName
Indicates a relationship where an entity is linked or connected to the name of a U.S. state.
-
D.
hasStateOrDistrict
Indicates that an entity is associated with, located in, or belongs to a particular state or district.
-
E.
associatedProvinceOrState
Indicates that one entity is linked or related to a specific province or state as its relevant administrative region.
- F. None of above.
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_69f2246fb2b88190acff36bf7975c8f0 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 29, 2026, 6:50 p.m.