Triple

T34865223
Position Surface form Disambiguated ID Type / Status
Subject Hutu–Tutsi E1004990 entity
Predicate historicallyPoliticized P168883 FINISHED
Object yes 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: yes | Statement: [Hutu–Tutsi, historicallyPoliticized, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicallyPoliticized
Context triple: [Hutu–Tutsi, historicallyPoliticized, yes]
  • A. politicallySignificant
    Indicates that an entity, event, or action has notable impact on, relevance to, or implications for political processes, power structures, or public policy.
  • B. historicallyOpposedBy
    Indicates that one entity has been the target of opposition, resistance, or antagonism from another entity over a historical period.
  • C. politicallyIn
    Indicates that one entity is located within, belongs to, or falls under the political jurisdiction or authority of another entity.
  • D. historicallyContested chosen
    Indicates that the relationship or status between entities has been the subject of historical dispute, disagreement, or competing claims over time.
  • E. hasPoliticalSignificanceFor
    Indicates that something holds importance, influence, or consequence within the political context or interests of a particular 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_69f76dbb678081909a247b9b5e1a73ac completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_6a008e29f76881908e656dbbd7fceea3 completed May 10, 2026, 1:54 p.m.
PD Predicate disambiguation batch_6a008dc01b308190bc26e69814692f82 completed May 10, 2026, 1:53 p.m.
Created at: May 3, 2026, 4 p.m.