Triple
T36711757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | India–US Civil Nuclear Agreement |
E906811
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | civil nuclear cooperation agreement |
C824
|
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: civil nuclear cooperation agreement Context triple: [India–US Civil Nuclear Agreement, instanceOf, civil nuclear cooperation agreement]
-
A.
international agreement
chosen
An international agreement is a formal, negotiated arrangement between two or more sovereign states or international organizations that creates binding obligations under international law.
-
B.
energy cooperation initiative
An energy cooperation initiative is a coordinated effort among multiple stakeholders—such as governments, organizations, or communities—to jointly develop, share, and manage energy resources, technologies, and policies for mutual benefit and sustainability.
-
C.
bilateral military agreement
A bilateral military agreement is a formal pact between two states that outlines mutual defense commitments, security cooperation, and related military obligations and activities.
-
D.
international agreement package
An international agreement package is a bundled set of formally negotiated documents, terms, and supporting materials that collectively define and govern a cross-border accord between participating entities or nations.
-
E.
bilateral diplomatic agreement
A bilateral diplomatic agreement is a formal, negotiated arrangement between two sovereign states that defines mutual rights, obligations, and cooperative actions in specific areas of shared interest.
- 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_69f76e73ad108190a5241585f2303e9a |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.