Triple

T10490090
Position Surface form Disambiguated ID Type / Status
Subject Jebel Marra E247392 entity
Predicate hasConflictImpact P57235 FINISHED
Object area affected by Darfur 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: area affected by Darfur conflict | Statement: [Jebel Marra, hasConflictImpact, area affected by Darfur conflict]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasConflictImpact
Context triple: [Jebel Marra, hasConflictImpact, area affected by Darfur conflict]
  • A. associatedConflictImpact chosen
    Indicates a relationship where an entity is linked to a specific conflict and the effects or consequences that conflict has on it.
  • B. hasUpstreamImpactOn
    Indicates that one entity’s actions, changes, or outputs affect another entity that is positioned earlier in a process, flow, or dependency chain.
  • C. triggersConflict
    Indicates that one entity initiates or causes a dispute, clash, or incompatibility to arise with another entity or within a system.
  • D. hasConflictRelatedDamage
    Indicates that an entity has incurred damage that is directly related to, or caused by, a conflict or conflict-related event.
  • E. hasConflictStatus
    Indicates that there exists a state of conflict or dispute associated with the relationship between the involved entities.
  • 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_69d381c309b88190af78aa681cf6a4c2 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d5097d61e08190952d4354ef1bce52 completed April 7, 2026, 1:41 p.m.
PD Predicate disambiguation batch_69d4fb8a30848190b33cf43f005a028e completed April 7, 2026, 12:41 p.m.
Created at: April 6, 2026, 12:23 p.m.