Triple

T5174401
Position Surface form Disambiguated ID Type / Status
Subject Ruggeller Riet E116760 entity
Predicate hasProtectionGoal P8850 FINISHED
Object conservation of wetland habitats 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: conservation of wetland habitats | Statement: [Ruggeller Riet, hasProtectionGoal, conservation of wetland habitats]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasProtectionGoal
Context triple: [Ruggeller Riet, hasProtectionGoal, conservation of wetland habitats]
  • A. protectionObjective chosen
    Indicates that one entity has the goal or purpose of safeguarding, defending, or preserving another entity or its interests.
  • B. hasPolicyGoal
    Indicates that an entity is associated with, or aims to achieve, a specific policy objective or target.
  • C. providesProtectionAgainst
    Indicates that one entity serves to guard, shield, or defend another entity from a specified harm, threat, or adverse effect.
  • D. isProtectedFor
    Indicates that one entity is safeguarded or preserved specifically for the benefit, use, or rights of another entity.
  • E. aimsToProtect
    Indicates an intention or purpose to safeguard or defend one entity, value, or condition from harm, risk, or undesirable outcomes.
  • 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_69bd445ff97c81909a2615cc56235470 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd7971284481909e6d07b2368a4f76 completed March 20, 2026, 4:44 p.m.
PD Predicate disambiguation batch_69bd77b529948190b86671ebe43f4734 completed March 20, 2026, 4:37 p.m.
Created at: March 20, 2026, 1:45 p.m.