Triple
T35980401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samizdat information service during Czechoslovak normalization |
E1040546
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | human rights documentation effort |
C11837
|
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 documentation effort Context triple: [Samizdat information service during Czechoslovak normalization, instanceOf, human rights documentation effort]
-
A.
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.
-
B.
human rights initiative
chosen
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 research center
A human rights research center is an organization dedicated to systematically studying, documenting, and analyzing human rights issues to inform policy, advocacy, and public awareness.
-
D.
human rights book
A human rights book is a written work that explores, explains, or documents the principles, history, laws, and real-world issues related to the protection and promotion of fundamental human freedoms and dignity.
-
E.
human rights blog
A human rights blog is an online platform that publishes articles, commentary, and resources focused on documenting, analyzing, and advocating for the protection and promotion of fundamental human rights.
- 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_69f76e28293c8190ae3f4e2208b87117 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.