Triple
T11735427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guru Tegh Bahadur |
E279013
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | human rights defender |
C1151
|
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 defender Context triple: [Guru Tegh Bahadur, instanceOf, human rights defender]
-
A.
human rights advocate
chosen
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.
human rights initiative
A human rights initiative is an organized effort or program aimed at promoting, protecting, and advancing fundamental human rights and freedoms for individuals or communities.
-
C.
human rights archive
A human rights archive is a curated collection of documents, testimonies, media, and other records that preserve, document, and provide evidence of human rights abuses and advocacy efforts over time.
-
D.
Uzbekistani human rights activist
An Uzbekistani human rights activist is an individual from Uzbekistan who advocates for the protection and promotion of civil, political, social, and cultural rights, often challenging government abuses and working to advance legal and social reforms.
-
E.
human rights mandate
A human rights mandate is an authoritative directive or framework that obliges institutions, governments, or organizations to respect, protect, and promote fundamental human rights in their policies, practices, and decision-making.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:41 p.m.