Triple

T23565161
Position Surface form Disambiguated ID Type / Status
Subject Canadian border near Fortuna, North Dakota E579350 entity
Predicate borderWithCanadianProvince P88549 FINISHED
Object Saskatchewan 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: Saskatchewan | Statement: [Canadian border near Fortuna, North Dakota, borderWithCanadianProvince, Saskatchewan]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: borderWithCanadianProvince
Context triple: [Canadian border near Fortuna, North Dakota, borderWithCanadianProvince, Saskatchewan]
  • A. hasBorderLengthWithCanada_km
    Indicates the length, in kilometers, of the land or maritime border that an entity shares with Canada.
  • B. bordersCanadianProvinceIndirectlyAcrossWater
    Indicates that one region is separated from a Canadian province only by a body of water, such that they face each other across water rather than sharing a direct land border.
  • C. borderingStateOrProvince chosen
    Indicates that one state or province shares a common boundary with another state or province.
  • D. provinceBordering
    Indicates that two provinces share a common boundary or border with each other.
  • E. countyBorder
    Indicates that two counties share a common boundary or border with each other.
  • 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_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.
Created at: April 17, 2026, 6:34 p.m.