Triple
T16663673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UMM |
E404923
|
entity |
| Predicate | city |
P40
|
FINISHED |
| Object | Morris, Minnesota |
E405965
|
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: Morris, Minnesota | Statement: [UMM, city, Morris, Minnesota]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Morris, Minnesota Context triple: [UMM, city, Morris, Minnesota]
-
A.
Morris, Minnesota
chosen
Morris, Minnesota is a small city in west-central Minnesota known for hosting the University of Minnesota Morris and serving as a regional educational and agricultural hub.
-
B.
Morristown, Minnesota
Morristown, Minnesota is a small rural city in southern Minnesota known for its close-knit community and local agricultural surroundings.
-
C.
Mora, Minnesota
Mora, Minnesota is a small city in east-central Minnesota that serves as the county seat of Kanabec County and a regional hub for the surrounding rural area.
-
D.
Montrose, Minnesota
Montrose, Minnesota is a small city in Wright County known for its rural character and proximity to the Twin Cities metropolitan area.
-
E.
Manchester, Minnesota
Manchester, Minnesota is a small rural community located in Freeborn County in southern Minnesota.
- 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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37c9afd048190b73bbc9c423915ca |
completed | April 18, 2026, 12:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a009d31372c8190b9d73a9b7db51f0f |
completed | May 10, 2026, 2:58 p.m. |
Created at: April 10, 2026, 5:18 a.m.