Triple
T31063472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Preventive Mechanisms |
E791607
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | torture prevention mechanism |
C57473
|
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: torture prevention mechanism Context triple: [National Preventive Mechanisms, instanceOf, torture prevention mechanism]
-
A.
torture facility
A torture facility is a controlled environment where individuals are deliberately subjected to severe physical or psychological pain, coercion, or degradation, typically for punishment, intimidation, or extracting information.
-
B.
torture experiment
A torture experiment is a deliberate, controlled infliction of severe physical or psychological pain on subjects to study their reactions or obtain information, typically in violation of ethical and legal standards.
-
C.
torturer
A torturer is an individual who deliberately inflicts severe physical or psychological pain on others, typically to punish, coerce, or extract information.
-
D.
child protection mechanism
A child protection mechanism is a system of policies, procedures, and tools designed to prevent, detect, and respond to abuse, neglect, or exploitation of children, ensuring their safety and well-being.
-
E.
human trafficking victim protection measure
A human trafficking victim protection measure is a policy, procedure, or intervention designed to identify, safeguard, and support individuals who have been trafficked, ensuring their safety, rights, and access to necessary services.
- 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_69f224cc0c5c81908404f087bff92997 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:01 p.m.