Triple
T34455917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minnesota and Ontario |
E884502
|
entity |
| Predicate | borderSupervisedBy |
P199881
|
FINISHED |
| Object | International Joint 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 Joint Commission | Statement: [Minnesota and Ontario, borderSupervisedBy, International Joint Commission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderSupervisedBy Context triple: [Minnesota and Ontario, borderSupervisedBy, International Joint Commission]
-
A.
borderMonitored
Indicates that a border between two regions or entities is actively being watched, controlled, or surveilled.
-
B.
borderConfirmedBy
Indicates that the existence or delineation of a border is validated or officially recognized by a specified authority or source.
-
C.
borderDefinedBy
Indicates that the boundary or limit of one entity is determined, shaped, or delineated by another entity.
-
D.
borderControls
Indicates that one entity enforces or administers border control measures over another entity or at a specific boundary.
-
E.
borderGuardDuty
Indicates that an entity is assigned to perform security or monitoring duties at a border or checkpoint.
- 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_69f349c607688190b553539d14901a35 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff6074bcd4819090b72cd6209ff206 |
completed | May 9, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69ff600aba888190812a6e7eca0283b8 |
completed | May 9, 2026, 4:25 p.m. |
| PDg | Predicate description generation | batch_69ff607407a881909d9e6e1c98559a6e |
completed | May 9, 2026, 4:27 p.m. |
Created at: May 1, 2026, 2 a.m.