Triple
T26086759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Afghan Boundary Commission |
E658004
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anglo-Russian joint commission |
C15820
|
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: Anglo-Russian joint commission Context triple: [Afghan Boundary Commission, instanceOf, Anglo-Russian joint commission]
-
A.
India–Russia military cooperation activity
India–Russia military cooperation activity encompasses the joint defense initiatives, arms trade, technology transfers, training exercises, and strategic collaborations undertaken between India and Russia to enhance their mutual security and military capabilities.
-
B.
World War I–era diplomatic agreement
A World War I–era diplomatic agreement is a formal treaty, pact, or understanding negotiated between states during or immediately surrounding the First World War, aimed at managing alliances, territorial claims, military commitments, or postwar settlements.
-
C.
bilateral commission
chosen
A bilateral commission is a formal joint body established by two parties, typically states or organizations, to negotiate, coordinate, and oversee matters of mutual interest.
-
D.
Mongolian–Russian joint venture
A Mongolian–Russian joint venture is a business entity jointly owned and operated by Mongolian and Russian partners, typically established to collaborate on commercial, industrial, or resource-based projects across the two countries.
-
E.
borough commission
A borough commission is a local governing body or administrative board responsible for overseeing municipal functions, services, and regulations within a specific borough.
- 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_69ee5bbf0d208190801ee95d4f07fb16 |
completed | April 26, 2026, 6:38 p.m. |
Created at: April 26, 2026, 7:43 p.m.