Triple
T32675123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No Nukes rally in New York City |
E835410
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | anti-nuclear power demonstration |
C379
|
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: anti-nuclear power demonstration Context triple: [No Nukes rally in New York City, instanceOf, anti-nuclear power demonstration]
-
A.
protest action
A protest action is a collective, organized public demonstration or activity undertaken to express opposition, support, or demand for social, political, economic, or environmental change.
-
B.
political protest
chosen
A political protest is a collective public action, such as demonstrations, marches, or rallies, through which people express opposition to or support for specific political decisions, policies, or authorities.
-
C.
protest dispersal
Protest dispersal is the coordinated process by which authorities or organizers attempt to break up, redirect, or conclude a public demonstration, often using legal orders, communication, and sometimes physical or tactical measures.
-
D.
nuclear power advocacy programme
A nuclear power advocacy programme is an organized initiative that promotes the adoption, expansion, and public acceptance of nuclear energy through education, policy engagement, and stakeholder outreach.
-
E.
anti-nuclear weapons document
An anti-nuclear weapons document is a written work that argues against the development, possession, or use of nuclear weapons, often advocating for disarmament, non-proliferation, and alternative security measures.
- 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_69f3493134b48190aa3c8cb523bd3800 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:09 a.m.