Triple
T24356579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montana–Alberta border area |
E613938
|
entity |
| Predicate | borderSurveyedBy |
P76064
|
FINISHED |
| Object | International Boundary Commission |
—
|
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: International Boundary Commission | Statement: [Montana–Alberta border area, borderSurveyedBy, International Boundary Commission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderSurveyedBy Context triple: [Montana–Alberta border area, borderSurveyedBy, International Boundary Commission]
-
A.
borderConfirmedBy
chosen
Indicates that the existence or delineation of a border is validated or officially recognized by a specified authority or source.
-
B.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
C.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
-
D.
borderStateOf
Indicates that one state shares a common boundary or border with another state.
-
E.
borderStateNearby
Indicates that one state is geographically close to, but does not necessarily directly touch, the border of another state.
- 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_69e2d7dfe7f08190b7a1f3a36483ab05 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29349ee188190a9d54b2c725b8a27 |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2 a.m.