Triple
T16354459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agreement on the principles of mutual relations between Afghanistan and Pakistan |
E397138
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Afghanistan–Pakistan treaty |
C566
|
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: Afghanistan–Pakistan treaty Context triple: [Agreement on the principles of mutual relations between Afghanistan and Pakistan, instanceOf, Afghanistan–Pakistan treaty]
-
A.
treaty
chosen
A treaty is a formal, legally binding agreement between two or more sovereign states or international entities that defines their mutual rights, obligations, and commitments.
-
B.
non‑aggression pact
A non-aggression pact is a formal agreement between two or more parties in which they commit not to engage in military or hostile actions against each other, typically for a specified period.
-
C.
border treaty
A border treaty is a formal agreement between two or more states that defines, clarifies, or adjusts their mutual territorial boundaries and the rules governing them.
-
D.
anti-Taliban alliance
A coalition of domestic and international actors united in political, military, and diplomatic efforts to oppose, resist, or undermine Taliban control and influence in Afghanistan.
-
E.
international agreement
An international agreement is a formal, negotiated arrangement between two or more sovereign states or international organizations that creates binding obligations under international law.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:07 a.m.