Triple

T23367651
Position Surface form Disambiguated ID Type / Status
Subject Cala Trebalúger E593367 entity
Predicate hasProtectedCharacter P152448 FINISHED
Object partially protected natural area 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: partially protected natural area | Statement: [Cala Trebalúger, hasProtectedCharacter, partially protected natural area]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasProtectedCharacter
Context triple: [Cala Trebalúger, hasProtectedCharacter, partially protected natural area]
  • A. hasGuardCharacter
    Indicates that one entity serves as a guard or protective character for another entity.
  • B. hasSpecialCharacter
    Indicates that a given entity (such as a string or identifier) contains at least one non-alphanumeric special character.
  • C. isProtectedFor
    Indicates that one entity is safeguarded or preserved specifically for the benefit, use, or rights of another entity.
  • D. hasLanguageCharacter
    Indicates that an entity uses, contains, or is associated with a specific written or symbolic character from a language.
  • E. isProtectedFrom
    Indicates that one entity is safeguarded or shielded against harm, damage, or adverse effects caused by another entity or factor.
  • F. None of above. chosen

Provenance (4 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_69e25d2593c88190bcdf4a716a94ccb2 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1a0ad621881908a909f236e6e9c90 completed April 29, 2026, 6:09 a.m.
PD Predicate disambiguation batch_69f061c7aaa48190a58ce93f87155ffc completed April 28, 2026, 7:29 a.m.
PDg Predicate description generation batch_69f0bd4a0e408190ad8916faf23562d9 completed April 28, 2026, 1:59 p.m.
Created at: April 17, 2026, 5:32 p.m.