Triple
T12813092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Webster–Ashburton Treaty negotiations |
E306319
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international diplomatic event |
C69
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: international diplomatic event Context triple: [Webster–Ashburton Treaty negotiations, instanceOf, international diplomatic event]
-
A.
international political conference
An international political conference is a formal gathering of representatives from multiple countries convened to discuss, negotiate, and coordinate policies on global or regional political issues.
-
B.
international political forum
An international political forum is a structured platform where representatives from multiple countries convene to discuss, negotiate, and coordinate on global political, economic, and security issues.
-
C.
international diplomatic document
An international diplomatic document is a formal written instrument exchanged between states or international organizations to record, communicate, or formalize agreements, positions, or understandings in the conduct of foreign relations.
-
D.
diplomatic conference
chosen
A diplomatic conference is a formal gathering of representatives from different states or international organizations convened to negotiate agreements, resolve disputes, or discuss issues of mutual concern.
-
E.
international initiative
An international initiative is a coordinated effort among multiple countries or global organizations aimed at addressing shared challenges or achieving common goals across national borders.
- F. None of above.
Provenance (1 batch)
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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:31 p.m.