Triple

T26583848
Position Surface form Disambiguated ID Type / Status
Subject Orupembe Conservancy E667150 entity
Predicate benefitSharing P83042 FINISHED
Object community income generation 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: community income generation | Statement: [Orupembe Conservancy, benefitSharing, community income generation]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: benefitSharing
Context triple: [Orupembe Conservancy, benefitSharing, community income generation]
  • A. benefitSharingIncludes chosen
    Indicates that the specified benefit-sharing arrangement encompasses or covers the referenced elements, parties, or mechanisms.
  • B. benefitSharingMechanismIncludes
    Indicates that a specified benefit-sharing mechanism contains, incorporates, or makes use of another defined component, method, or arrangement for sharing benefits.
  • C. benefitSharingFundSupports
    Indicates that a benefit-sharing fund provides financial or material support to a project, activity, or recipient.
  • D. shareConservationArea
    Indicates that two or more entities have a conservation area that overlaps or is jointly designated or managed.
  • E. sharesTaxaWith
    Indicates that two entities have one or more taxonomic groups (taxa) in common.
  • 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_69ee9cfb7e548190b60a9031182f5a7e completed April 26, 2026, 11:17 p.m.
NER Named-entity recognition batch_69f63fd6c68481908c542aa03e297b9c completed May 2, 2026, 6:17 p.m.
PD Predicate disambiguation batch_69f63c663be481908f233d25d28713a4 completed May 2, 2026, 6:03 p.m.
Created at: April 27, 2026, 2:04 a.m.