Triple
T34455930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minnesota and Ontario |
E884502
|
entity |
| Predicate | borderPartOf |
P115250
|
FINISHED |
| Object | Canada–United States 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: Canada–United States border | Statement: [Minnesota and Ontario, borderPartOf, Canada–United States border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderPartOf Context triple: [Minnesota and Ontario, borderPartOf, Canada–United States border]
-
A.
borderSectionOf
chosen
Indicates that one entity represents a specific segment or portion of the overall border of another entity.
-
B.
formsPartOfBorderType
Indicates that one border type constitutes a component or segment of another, more comprehensive border type.
-
C.
partlyFormsBorderBetween
Indicates that one entity constitutes only a portion of the boundary separating two other entities.
-
D.
borderWithin
Indicates that one region’s border lies entirely inside the boundary of another region.
-
E.
deltaPartOf
Indicates that one entity represents a changed, differing, or modified portion of another entity, rather than the whole.
- 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_69f349c607688190b553539d14901a35 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff63225b6481909217ad11b4f7d3ba |
completed | May 9, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ff60e0882c819085d097010db43ee0 |
completed | May 9, 2026, 4:29 p.m. |
Created at: May 1, 2026, 2 a.m.