Triple
T38466573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East North Central division |
E912582
|
entity |
| Predicate | containsInternationalBorder |
P70709
|
FINISHED |
| Object | United States–Canada border |
E131553
|
NE 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: United States–Canada border | Statement: [East North Central division, containsInternationalBorder, United States–Canada border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsInternationalBorder Context triple: [East North Central division, containsInternationalBorder, United States–Canada border]
-
A.
hasInternationalBorderSection
chosen
Indicates that one entity shares a specific segment or portion of its international border with another entity.
-
B.
hasBorderWithinCountry
Indicates that one region or area shares an internal boundary with another region or area within the same country.
-
C.
nearInternationalBoundary
Indicates that one entity is located close to an international boundary separating two or more countries.
-
D.
hasBorderMeetingCountry
Indicates that one country shares a land or maritime border with another country.
-
E.
hasCountryBorderWith
Indicates that two countries share a common land or maritime boundary.
- F. None of above.
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_69f76e861d8c81908559031dc66e3c15 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a021706e21c81909b83e2b4d9c4130c |
completed | May 11, 2026, 5:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41d6498f9481909895f9639e32ea76 |
completed | June 29, 2026, 2:19 a.m. |
| PD | Predicate disambiguation | batch_6a0216861214819097d2177755bc19d7 |
completed | May 11, 2026, 5:48 p.m. |
Created at: May 3, 2026, 4:31 p.m.