Triple
T23321262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rage Against the Machine for Christmas No.1 (2009) |
E591155
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | grassroots music campaign |
C29274
|
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: grassroots music campaign Context triple: [Rage Against the Machine for Christmas No.1 (2009), instanceOf, grassroots music campaign]
-
A.
civil society campaign
A civil society campaign is a coordinated effort by non-governmental organizations, community groups, and citizens to advocate for social, political, or environmental change through public engagement and policy influence.
-
B.
community engagement campaign
chosen
A community engagement campaign is a coordinated set of activities and communications designed to inform, involve, and motivate community members to participate in achieving a shared goal or addressing a common issue.
-
C.
civil rights music group
A civil rights music group is an ensemble of musicians who create and perform songs that advocate for social justice, equality, and the protection of civil liberties, often aligning their work with specific movements or campaigns.
-
D.
urban folk music
Urban folk music is a genre that blends traditional folk melodies and storytelling with contemporary urban influences, instruments, and production styles to reflect modern city life and social issues.
-
E.
public campaign
A public campaign is a coordinated set of communication and outreach activities designed to inform, persuade, or mobilize a broad audience around a specific social, political, or commercial issue.
- 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_69e25d1effe4819096907f95f610dbff |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:07 p.m.