Triple
T28948637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Dakota–Minnesota border |
E730946
|
entity |
| Predicate | riverFormsBoundaryFor |
P31306
|
FINISHED |
| Object | Cass County, North Dakota – Clay County, 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: Cass County, North Dakota – Clay County, Minnesota | Statement: [North Dakota–Minnesota border, riverFormsBoundaryFor, Cass County, North Dakota – Clay County, Minnesota]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverFormsBoundaryFor Context triple: [North Dakota–Minnesota border, riverFormsBoundaryFor, Cass County, North Dakota – Clay County, Minnesota]
-
A.
riverFormsBorderWith
chosen
Indicates that a river serves as a boundary line between two geographic or political entities.
-
B.
formsBoundaryType
Indicates that one entity serves as a specific type of boundary for another entity.
-
C.
formsShorelineOf
Indicates that one geographic feature constitutes or defines the boundary or edge (shoreline) of a body of water.
-
D.
statesBoundOfForm
Indicates that one state or condition serves as a boundary or limiting form for another.
-
E.
outerBoundary
Indicates that one entity serves as the enclosing outer limit or perimeter that bounds another entity or region.
- 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_69f043eb9bcc819091ac7b07aecb6475 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 28, 2026, 8:42 a.m.