Triple
T32315404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Sioux Community |
E825617
|
entity |
| Predicate | hasSettlementNear |
P51472
|
FINISHED |
| Object | Granite Falls, Minnesota |
—
|
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: Granite Falls, Minnesota | Statement: [Upper Sioux Community, hasSettlementNear, Granite Falls, Minnesota]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSettlementNear Context triple: [Upper Sioux Community, hasSettlementNear, Granite Falls, Minnesota]
-
A.
hasSettlementAround
chosen
Indicates that a settlement is located in the surrounding area of a specified place or feature.
-
B.
possibleSettlementAt
Indicates that a settlement could potentially be established or located at a given place or site.
-
C.
isSettlement
Indicates that the subject entity functions as a human-inhabited place or community, such as a town, village, or city.
-
D.
isSettlementAlong
Indicates that a settlement is located adjacent to or in close proximity along the course or edge of a specified linear feature, such as a river, road, or coastline.
-
E.
hasHumanSettlement
Indicates that a location or area contains or is the site of a human settlement, such as a town, village, or city.
- 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff49016dcc8190a8a43868c728b4f1 |
completed | May 9, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69ff4891924c8190b5be340e2520e012 |
completed | May 9, 2026, 2:45 p.m. |
Created at: May 1, 2026, 12:46 a.m.