Triple
T32413581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muttahida Majlis-e-Amal |
E828286
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | political party alliance in Pakistan |
C49023
|
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: political party alliance in Pakistan Context triple: [Muttahida Majlis-e-Amal, instanceOf, political party alliance in Pakistan]
-
A.
Pakistani political party
A Pakistani political party is an organized group of individuals in Pakistan that shares a common political ideology or agenda and seeks to gain and exercise governmental power through participation in elections and public policymaking.
-
B.
Indian political alliance
An Indian political alliance is a coalition of two or more political parties in India that collaborate to contest elections, share resources, and pursue common policy goals while retaining their individual identities.
-
C.
group of political parties
chosen
A group of political parties is a collection of distinct political organizations that coordinate or align to pursue shared ideological goals, policy agendas, or electoral strategies.
-
D.
political alliance strategy
A political alliance strategy is a coordinated plan by which parties or actors form, manage, and leverage partnerships to maximize power, influence policy outcomes, and achieve shared or complementary political goals.
-
E.
Italian political alliance
An Italian political alliance is a coalition of two or more Italian political parties that coordinate their electoral strategies and policy platforms to increase their collective influence in government and parliament.
- 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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:53 a.m.