Triple
T19873114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dakota County, Nebraska |
E477569
|
entity |
| Predicate | ISOCode |
P208
|
FINISHED |
| Object | US-NE |
—
|
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: US-NE | Statement: [Dakota County, Nebraska, ISOCode, US-NE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: US-NE Context triple: [Dakota County, Nebraska, ISOCode, US-NE]
-
A.
US-NE
chosen
US-NE is the ISO 3166-2 code representing the U.S. state of Nebraska.
-
B.
N.E.
N.E. is the standard legal citation abbreviation for the North Eastern Reporter, a regional case law reporter covering appellate decisions from several U.S. states.
-
C.
US-MN
US-MN is the postal abbreviation for the U.S. state of Minnesota.
-
D.
Kansa
Kansa is another name for the Kaw Nation, a Native American tribe originally from the central Midwestern region of the United States, particularly present-day Kansas.
-
E.
Northern United States
The Northern United States is the broad region of U.S. states that stretch along the country’s northern border, characterized by colder climates, significant industrial and urban centers, and proximity to Canada.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e51e7d948190aedbcd6c30361c39 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e658d92f9c8190b363587ed1881c2c |
completed | April 20, 2026, 4:48 p.m. |
Created at: April 10, 2026, 1:51 p.m.