Triple
T10305961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James River |
E241760
|
entity |
| Predicate | hasCityOnBank |
P7935
|
FINISHED |
| Object | Huron, South Dakota |
E857540
|
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: Huron, South Dakota | Statement: [James River, hasCityOnBank, Huron, South Dakota]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Huron, South Dakota Context triple: [James River, hasCityOnBank, Huron, South Dakota]
-
A.
Huron, South Dakota
chosen
Huron, South Dakota is a small city in east-central South Dakota known as a regional agricultural and commercial hub on the prairie.
-
B.
Hudson, South Dakota
Hudson, South Dakota is a small rural town located in southeastern South Dakota near the Iowa border.
-
C.
Humboldt, South Dakota
Humboldt, South Dakota is a small rural town in eastern South Dakota located just west of Sioux Falls.
-
D.
Hartford, South Dakota
Hartford, South Dakota is a small city in eastern South Dakota that serves as a growing residential community near Sioux Falls.
-
E.
Parmelee, South Dakota
Parmelee, South Dakota is a small community located within the Rosebud Indian Reservation and is part of the homeland of the Sicangu Lakota (Rosebud Sioux) Tribe.
- 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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d309a4508190ad9de37171a64dba |
completed | April 7, 2026, 9:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d7fb5cbaec8190a9773f8d72d51c1a |
completed | April 9, 2026, 7:17 p.m. |
Created at: April 6, 2026, 11:46 a.m.