Triple
T28948642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Dakota–Minnesota border |
E730946
|
entity |
| Predicate | naturalBoundaryType |
P155478
|
FINISHED |
| Object | river boundary |
—
|
LITERAL 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: river boundary | Statement: [North Dakota–Minnesota border, naturalBoundaryType, river boundary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: naturalBoundaryType Context triple: [North Dakota–Minnesota border, naturalBoundaryType, river boundary]
-
A.
boundaryCondition
Indicates the specific constraints or values imposed at the limits or edges of a system, domain, or process that govern its behavior there.
-
B.
formsBoundaryType
Indicates that one entity serves as a specific type of boundary for another entity.
-
C.
typicalBoundary
Indicates that one entity serves as the usual or characteristic boundary or limit for another entity.
-
D.
boundaryCurrentType
Indicates the specific kind or classification of the current that exists at or across a boundary between regions or components.
-
E.
hasNaturalBorder
chosen
Indicates that one entity’s boundary with another is formed or defined by a natural feature such as a river, mountain range, coastline, or desert.
- 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_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 8:42 a.m.