Triple
T27172847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tashnag Party |
E682966
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Armenian political party |
C52581
|
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: Armenian political party Context triple: [Tashnag Party, instanceOf, Armenian political party]
-
A.
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.
-
B.
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.
-
C.
Tunisian political party
A Tunisian political party is an organized group of individuals in Tunisia that shares a common political ideology or agenda and seeks to influence or control government policy and leadership through participation in elections and public affairs.
-
D.
Romanian political party
A Romanian political party is an organized group of individuals in Romania that shares a common political ideology or set of policy goals and seeks to gain and exercise political power through participation in elections and governance.
-
E.
Hungarian political party
A Hungarian political party is an organized group within Hungary that seeks to influence or control government policy and leadership by contesting elections and representing specific ideological, social, or economic interests.
- F. None of above. chosen
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_69eefad086808190ab89816c0c300476 |
completed | April 27, 2026, 5:57 a.m. |
Created at: April 27, 2026, 9:24 a.m.