Triple
T19703175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | For Truth |
E473145
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian political party |
C42374
|
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: Russian political party Context triple: [For Truth, instanceOf, Russian political party]
-
A.
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.
-
B.
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.
-
C.
political party
A political party is an organized group of people who share common political ideals and policy goals and work together to gain and exercise governmental power through elections and public influence.
-
D.
партия Российской империи
Политическая партия Российской империи — это организованное объединение людей с общими политическими взглядами и программой, созданное для участия в политической жизни и влияния на государственную власть в условиях монархического строя Российской империи.
-
E.
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.
- 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:46 p.m.