Triple

T34475409
Position Surface form Disambiguated ID Type / Status
Subject Foča municipality E885018 entity
Predicate hasTypeOfCrimeRecognizedAs P49668 FINISHED
Object crimes against humanity 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: crimes against humanity | Statement: [Foča municipality, hasTypeOfCrimeRecognizedAs, crimes against humanity]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTypeOfCrimeRecognizedAs
Context triple: [Foča municipality, hasTypeOfCrimeRecognizedAs, crimes against humanity]
  • A. hasClassifiedCrime
    Indicates that an entity has been assigned or associated with a specific crime category or classification.
  • B. recognitionOfCrimes chosen
    Indicates the formal acknowledgment or identification that certain actions or events constitute crimes under a legal or normative framework.
  • C. hasCrimeElement
    Indicates that a situation, action, or entity involves or contains a component that is legally recognized as part of a crime.
  • D. hasCrimeLevel
    Indicates the degree or severity of criminal activity associated with an entity or area.
  • E. hasCrimeGroup
    Indicates a relationship where an entity is associated with, belongs to, or is controlled by a particular criminal group or organization.
  • 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_69f349c880408190ade571c471ab154a completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69ff2fbae9b48190847eefa1c227d43e completed May 9, 2026, 12:59 p.m.
PD Predicate disambiguation batch_69ff2f2218048190a32224a648182b5d completed May 9, 2026, 12:57 p.m.
Created at: May 1, 2026, 2:01 a.m.