Triple

T27667917
Position Surface form Disambiguated ID Type / Status
Subject Evil Relations E697277 entity
Predicate hasPerpetratorGroup P81195 FINISHED
Object Moors murderers NE NERFINISHED

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: Moors murderers | Statement: [Evil Relations, hasPerpetratorGroup, Moors murderers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPerpetratorGroup
Context triple: [Evil Relations, hasPerpetratorGroup, Moors murderers]
  • A. hasPerpetrators chosen
    Indicates that certain entities are responsible for carrying out, committing, or executing a particular act, event, or wrongdoing.
  • B. hasPersecutedGroup
    Indicates that an entity has carried out systematic oppression, harassment, or harmful actions against a particular group.
  • C. hasCrimeGroup
    Indicates a relationship where an entity is associated with, belongs to, or is controlled by a particular criminal group or organization.
  • D. hasPerpetratorOrigin
    Indicates that the origin or source of a perpetrator (such as their nationality, place of birth, or background) is associated with a particular event, action, or crime.
  • E. accusedGroup
    Indicates that one group is formally charged or blamed by another party for committing a wrongdoing or offense.
  • 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_69ef590b85a4819083ec7c12bd3c9c10 completed April 27, 2026, 12:39 p.m.
NER Named-entity recognition batch_69f739a638748190808e7a2930dce16e completed May 3, 2026, 12:03 p.m.
PD Predicate disambiguation batch_69f732f2dc6c8190a4e86da98cc5eb05 completed May 3, 2026, 11:35 a.m.
Created at: April 27, 2026, 2:39 p.m.