Triple
T2076033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LGBT rights movement |
E44925
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | human rights 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: human rights movement Context triple: [LGBT rights movement, instanceOf, human rights movement]
-
A.
human rights advocate
A human rights advocate is an individual who actively works to protect, promote, and advance the fundamental rights and freedoms of all people through education, policy influence, legal action, and public engagement.
-
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.
resistance movement
A resistance movement is an organized effort by a group of people to oppose, undermine, or overthrow an existing power, authority, or occupying force, often through political, social, or guerrilla actions.
-
D.
labour movement
The labour movement is a collective social and political effort by workers and their organizations to improve wages, working conditions, and rights through solidarity, negotiation, and activism.
-
E.
United Nations human rights review mechanism
A United Nations human rights review mechanism is a formal, periodic process through which UN bodies assess and monitor states’ compliance with international human rights obligations, typically involving state reports, independent expert or peer review, and public recommendations for improvement.
- 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_69a88916c2b48190a5ca2e9b12cad3ed |
completed | March 4, 2026, 7:33 p.m. |
Created at: March 4, 2026, 7:41 p.m.