Triple
T22808594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian National Congress resolutions |
E564606
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | political resolution collection |
C27414
|
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 resolution collection Context triple: [Indian National Congress resolutions, instanceOf, political resolution collection]
-
A.
Communist Party resolution
chosen
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.
-
B.
Communist Party of Russia resolution
A Communist Party of Russia resolution is a formal, collectively adopted document that outlines the party’s official position, decisions, or directives on specific political, ideological, or organizational issues within the Russian context.
-
C.
political organization
A political organization is a structured group of individuals who collectively pursue specific political goals, such as influencing public policy, gaining or maintaining power, or representing particular interests within a political system.
-
D.
political work
Political work is the organized set of activities aimed at influencing, shaping, or implementing public policy, governance, and collective decision-making within a society.
-
E.
political section
A political section is a designated part of a publication, platform, or organization focused on news, analysis, and commentary related to government, public policy, elections, and political affairs.
- 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_69e245823f4c8190ade442cdcc2c224a |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:32 p.m.