Triple
T636252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wisconsin |
E16627
|
entity |
| Predicate | hasISOCode |
P189
|
FINISHED |
| Object | US-WI |
E16627
|
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-WI | Statement: [Wisconsin, hasISOCode, US-WI]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: US-WI Context triple: [Wisconsin, hasISOCode, US-WI]
-
A.
Wisconsin
chosen
Wisconsin is a U.S. state in the Upper Midwest known for its dairy industry, Great Lakes shorelines, and mix of rural landscapes and industrial cities.
-
B.
Madison, Wisconsin, United States
Madison, Wisconsin, United States is the capital city of Wisconsin, known for its major research university, vibrant cultural scene, and numerous lakes.
-
C.
Northeastern Wisconsin
Northeastern Wisconsin is a region of Wisconsin that includes the city of Green Bay and surrounding communities along the western shore of Lake Michigan and the Fox River Valley.
-
D.
US-CT
US-CT is the ISO 3166-2 code representing the U.S. state of Connecticut.
-
E.
US-MS
US-MS is the ISO 3166-2 code representing the U.S. state of Mississippi.
- 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49ee667f08190a0332b8f6c569e1a |
completed | March 1, 2026, 8:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a57405d6f48190b55542d50d3a1f22 |
completed | March 2, 2026, 11:27 a.m. |
Created at: March 1, 2026, 7:35 p.m.