Triple

T36596856
Position Surface form Disambiguated ID Type / Status
Subject Good Men E902825 entity
Predicate persecutedInEvent P33150 FINISHED
Object Albigensian Crusade 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: Albigensian Crusade | Statement: [Good Men, persecutedInEvent, Albigensian Crusade]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: persecutedInEvent
Context triple: [Good Men, persecutedInEvent, Albigensian Crusade]
  • A. persecutedDuring
    Indicates that one entity systematically harassed, oppressed, or victimized another entity during a specified time period or event.
  • B. persecutedIn chosen
    Indicates that an entity is subjected to oppression, harassment, or unfair treatment within a particular place, context, or time period.
  • C. persecutedAfter
    Indicates that one entity is subjected to persecution by another entity after a specified event or point in time.
  • D. persecutionOf
    Indicates the act of subjecting an entity to persistent, often unjust hostility, harassment, or oppression, typically on the basis of identity, beliefs, or group membership.
  • E. wasPersecutedBy
    Indicates that an entity was subjected to persistent hostility, oppression, or harmful treatment carried out by another entity.
  • 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_69f76e66b7b88190848f7a3e1188915f completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7c371931c8190afb1d4dd5157f92c completed May 3, 2026, 9:51 p.m.
PD Predicate disambiguation batch_69f7c1baf25c8190a78dd54a400d2c50 completed May 3, 2026, 9:44 p.m.
Created at: May 3, 2026, 4:11 p.m.