Triple
T13443747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revolutionary Communist Party, USA |
E320428
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | communist political party |
C347
|
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: communist political party Context triple: [Revolutionary Communist Party, USA, instanceOf, communist political party]
-
A.
communist-rooted party
A communist-rooted party is a political organization whose origins, ideology, or foundational structure are significantly shaped by Marxist-Leninist or other communist principles, even if its current platform has evolved or moderated over time.
-
B.
political party
chosen
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.
-
C.
Communist
A Communist is an individual who advocates for a classless, stateless society in which the means of production are collectively owned and resources are distributed according to need.
-
D.
Communist Party resolution
A Communist Party resolution is a formal, collectively adopted document that articulates the party’s official position, policies, or strategic directives on specific political, ideological, or organizational issues.
-
E.
political party member
A political party member is an individual who formally affiliates with a political organization, supporting its ideology, policies, and candidates through participation in its activities and decision-making processes.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:40 p.m.