Triple
T23756021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | India–Iran Chabahar Agreement |
E587117
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | strategic partnership agreement |
C17881
|
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: strategic partnership agreement Context triple: [India–Iran Chabahar Agreement, instanceOf, strategic partnership agreement]
-
A.
strategic partnership
A strategic partnership is a long-term, collaborative relationship between two or more independent organizations that align resources, capabilities, and objectives to achieve mutually beneficial competitive advantages they could not easily attain alone.
-
B.
partnership agreement
chosen
A partnership agreement is a legally binding contract between two or more parties that defines their business relationship, including ownership shares, roles, responsibilities, profit and loss distribution, and procedures for decision-making and dispute resolution.
-
C.
business partnership
A business partnership is a formal arrangement in which two or more individuals or entities share ownership, responsibilities, risks, and profits in operating a business.
-
D.
regional partnership
A regional partnership is a collaborative alliance among organizations, governments, or stakeholders within a specific geographic area to coordinate resources, strategies, and initiatives toward shared economic, social, or environmental goals.
-
E.
partnership structure
A partnership structure is an organizational arrangement in which two or more parties share ownership, responsibilities, risks, and profits according to agreed-upon terms.
- 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_69e2490a0eec81908cdef8a862828d7a |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 7:14 p.m.