Triple
T29575375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Peace and Friendship 1950 |
E753429
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | treaty between India and Nepal |
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: treaty between India and Nepal Context triple: [Treaty of Peace and Friendship 1950, instanceOf, treaty between India and Nepal]
-
A.
India–Bhutan cooperation initiative
The India–Bhutan cooperation initiative is a bilateral framework that promotes strategic, economic, cultural, and developmental collaboration between India and Bhutan through joint projects, capacity-building, and policy coordination.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
Created at: April 28, 2026, 6:02 p.m.