Triple

T5992221
Position Surface form Disambiguated ID Type / Status
Subject East Region (Cameroon) E133375 entity
Predicate hasActivityImpact P17691 FINISHED
Object deforestation from logging 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: deforestation from logging | Statement: [East Region (Cameroon), hasActivityImpact, deforestation from logging]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasActivityImpact
Context triple: [East Region (Cameroon), hasActivityImpact, deforestation from logging]
  • A. hasUpstreamImpactOn
    Indicates that one entity’s actions, changes, or outputs affect another entity that is positioned earlier in a process, flow, or dependency chain.
  • B. hasActivityIn
    Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
  • C. hasSignificantActivity
    Indicates that an entity exhibits a notable level or intensity of activity, performance, or operation relative to a defined threshold or context.
  • D. hasAct
    Indicates that an entity performs, participates in, or is associated with a specific act or action.
  • E. hasNotableImpact chosen
    Indicates that one entity exerts a significant or noteworthy influence or effect on another entity or context.
  • 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_69c0087010d081908bb8142342d63330 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c04e8fd030819095a4f3b3d425ec21 completed March 22, 2026, 8:18 p.m.
PD Predicate disambiguation batch_69c049e152e88190979ab80cb9b50321 completed March 22, 2026, 7:58 p.m.
Created at: March 22, 2026, 4:05 p.m.