Triple
T29274849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Human Rights Council Resolution S-9/1 |
E742219
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | human rights resolution |
C55156
|
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 resolution Context triple: [United Nations Human Rights Council Resolution S-9/1, instanceOf, human rights resolution]
-
A.
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.
-
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 case
A human rights case is a legal or quasi-legal proceeding in which an individual, group, or entity alleges that fundamental rights or freedoms protected by law have been violated, seeking recognition, remedy, or enforcement.
-
D.
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.
-
E.
human rights law
Human rights law is the body of international and domestic legal norms that protects the fundamental rights and freedoms inherent to all individuals against abuse by states and other actors.
- F. None of above. chosen
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_69f0912124d48190a046642b69407f4c |
completed | April 28, 2026, 10:51 a.m. |
Created at: April 28, 2026, 12:50 p.m.