Triple

T3673819
Position Surface form Disambiguated ID Type / Status
Subject Ad extirpanda E77940 entity
Predicate restrictionOnTorture P1050 FINISHED
Object forbade mutilation or danger of death LITERAL FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: forbade mutilation or danger of death | Statement: [Ad extirpanda, restrictionOnTorture, forbade mutilation or danger of death]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: restrictionOnTorture
Context triple: [Ad extirpanda, restrictionOnTorture, forbade mutilation or danger of death]
  • A. methodOfPersecution
    Indicates the specific means, technique, or process by which an act of persecution is carried out.
  • B. restriction chosen
    Indicates a limiting condition or rule that constrains or controls what an entity can do, use, or access in relation to another entity or context.
  • C. persecutedIn
    Indicates that an entity is subjected to oppression, harassment, or unfair treatment within a particular place, context, or time period.
  • D. subjectOfCondemnation
    Indicates that one entity is the target or object of formal disapproval, criticism, or denunciation by another entity.
  • E. restraintType
    Indicates the specific kind or method of restraint applied in a given situation or relationship.
  • F. None of above.

Provenance (3 batches)

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_69ad85e083008190b2e1b7085fe500bd completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc45fbd1c819099023791452f1beb completed March 8, 2026, 6:47 p.m.
PD Predicate disambiguation batch_69adb84a20288190a092e4a1b045fe3f completed March 8, 2026, 5:56 p.m.
Created at: March 8, 2026, 3:25 p.m.