Triple

T9126178
Position Surface form Disambiguated ID Type / Status
Subject SLORC E218971 entity
Predicate ethnicConflictInvolved P85501 FINISHED
Object Karen conflict 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: Karen conflict | Statement: [SLORC, ethnicConflictInvolved, Karen conflict]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ethnicConflictInvolved
Context triple: [SLORC, ethnicConflictInvolved, Karen conflict]
  • A. ethnoPoliticalConflict chosen
    Indicates a relationship in which groups defined by ethnic identity are engaged in political struggle, tension, or violence against one another or against a governing authority.
  • B. politicalConflict
    Indicates a relationship where entities are engaged in opposing political positions, struggles, or disputes, often involving competition for power, influence, or policy outcomes.
  • C. conflictCountry
    Indicates that there is an armed conflict or war involving the referenced country as a participant.
  • D. regionOfConflict
    Indicates that a specified region is the location where a particular conflict or dispute takes place.
  • E. religiousConflictBetween
    Indicates a relationship where two entities are in opposition or dispute due to differing religious beliefs, practices, or affiliations.
  • 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_69ca83dddd548190983b96c664f7f367 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cca8c93d3c8190b003b2b1af2003b2 completed April 1, 2026, 5:10 a.m.
PD Predicate disambiguation batch_69cc66003e3c819091e1e42c9cf7c781 completed April 1, 2026, 12:25 a.m.
Created at: March 30, 2026, 7:18 p.m.