Triple
T16353813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hezb-e Watan |
E397121
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Afghan political party |
C22998
|
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: Afghan political party Context triple: [Hezb-e Watan, instanceOf, Afghan political party]
-
A.
Afghan political organization
chosen
An Afghan political organization is a structured group operating within Afghanistan’s political sphere that seeks to influence governance, policy, and public opinion through formal or informal means.
-
B.
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.
-
C.
Iraqi political party
An Iraqi political party is an organized group within Iraq that seeks to influence or control government policy and leadership through participation in the country’s political processes and elections.
-
D.
Kurdish political organization
A Kurdish political organization is a structured group that represents Kurdish interests and identity, seeking to influence governance, policy, and self-determination through political, social, and sometimes armed activities.
-
E.
regional federation of political parties
A regional federation of political parties is an alliance of multiple political parties from different countries within a specific geographic region that coordinate policies, strategies, and representation to advance shared ideological or regional interests.
- 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.