Triple
T37235711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manitoba–Saskatchewan border |
E923566
|
entity |
| Predicate | touchesUSState |
P187670
|
FINISHED |
| Object | North Dakota |
—
|
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: North Dakota | Statement: [Manitoba–Saskatchewan border, touchesUSState, North Dakota]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: touchesUSState Context triple: [Manitoba–Saskatchewan border, touchesUSState, North Dakota]
-
A.
usedByUSStatePortion
Indicates that something (such as a resource, facility, or infrastructure) is utilized or operated by a specific portion or subdivision of a U.S. state.
-
B.
isInUSState
Indicates that one entity (typically a place or location) is geographically located within the boundaries of a specific U.S. state.
-
C.
nearestStateOrTerritory
Indicates that one location is the closest state or territory to another location, typically in terms of geographic distance.
-
D.
usedByStateOrTerritory
Indicates that something (such as an object, system, or resource) is utilized or employed by a specific state or territory.
-
E.
stateOfTerritory
Indicates the political or administrative state that has authority over a given territory.
- F. None of above. chosen
Provenance (4 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_69f76ea9fee88190a589f661d95a7189 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb78c982ac8190846efe8f6209e5d1 |
completed | May 6, 2026, 5:22 p.m. |
Created at: May 3, 2026, 4:15 p.m.