Triple
T2891064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Human Rights Program (University of Virginia School of Law) |
E63823
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | human rights education initiative |
C249
|
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 education initiative Context triple: [Human Rights Program (University of Virginia School of Law), instanceOf, human rights education initiative]
-
A.
human rights clinic
A human rights clinic is an educational and advocacy program, often within a law school or university, where students and practitioners work together to address real-world human rights issues through research, legal representation, and policy initiatives.
-
B.
human rights concept
A human rights concept is an abstract principle or idea that defines the fundamental freedoms, protections, and dignities to which every person is inherently entitled.
-
C.
educational movement
chosen
An educational movement is a coordinated effort by individuals or groups to reform, innovate, or transform teaching and learning practices, policies, or philosophies within an educational system or society.
-
D.
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.
-
E.
work on education
Work on education encompasses the theories, practices, and activities aimed at improving teaching, learning, and educational systems to foster knowledge, skills, and personal development.
- 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_69ab4c45822c8190830c5f2bb97bcfd0 |
completed | March 6, 2026, 9:51 p.m. |
Created at: March 6, 2026, 10:07 p.m.