Triple
T19939344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kerala Congress movement |
E479262
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional political movement |
C881
|
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: regional political movement Context triple: [Kerala Congress movement, instanceOf, regional political movement]
-
A.
regional politics
Regional politics is the study and practice of how political power, policies, and relationships operate within and between specific geographic areas or subnational units, such as states, provinces, or regions.
-
B.
political movement
chosen
A political movement is a collective effort by a group of people, often organized around shared ideas or grievances, seeking to influence or change government policies, social structures, or political power.
-
C.
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.
-
D.
regional election
A regional election is a formal process in which eligible voters within a specific subnational area (such as a state, province, or region) choose representatives or leaders for regional governing bodies.
-
E.
organ of a political movement
An organ of a political movement is a structured entity—such as a committee, publication, or media outlet—formally tasked with expressing, implementing, or coordinating the movement’s policies, strategies, and communications.
- 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:53 p.m.