Triple
T23565163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian border near Fortuna, North Dakota |
E579350
|
entity |
| Predicate | borderSectionNumber |
P153175
|
FINISHED |
| Object | North Dakota–Saskatchewan border |
—
|
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–Saskatchewan border | Statement: [Canadian border near Fortuna, North Dakota, borderSectionNumber, North Dakota–Saskatchewan border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderSectionNumber Context triple: [Canadian border near Fortuna, North Dakota, borderSectionNumber, North Dakota–Saskatchewan border]
-
A.
borderSectionOf
Indicates that one entity represents a specific segment or portion of the overall border of another entity.
-
B.
borderSectionLength
Indicates the measured length of a specific segment of a shared border between two geographic or administrative areas.
-
C.
borderSectionName
Indicates the specific named segment or portion of a border that is associated with or applies to an entity.
-
D.
borderArea
Indicates that an area lies along or near the boundary between two regions, countries, or territories.
-
E.
borderPoint
Indicates a point that lies on the boundary between two regions or entities.
- 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_69e245fe24588190888f3aec8407d8e3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1af6c2930819090bc2b95725fbf18 |
completed | April 29, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f12760784c8190aaeff002ef31febe |
completed | April 28, 2026, 9:32 p.m. |
Created at: April 17, 2026, 6:34 p.m.