Triple

T9598689
Position Surface form Disambiguated ID Type / Status
Subject Mediterranean maquis E231795 entity
Predicate hasEcologicalProcess P89145 FINISHED
Object fire regime 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: fire regime | Statement: [Mediterranean maquis, hasEcologicalProcess, fire regime]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasEcologicalProcess
Context triple: [Mediterranean maquis, hasEcologicalProcess, fire regime]
  • A. hasEcology
    Indicates that an entity has a particular ecological context, such as its habitat, environmental role, or interactions within an ecosystem.
  • B. hasEcosystemService
    Indicates that one entity provides, supports, or is associated with an ecosystem service that benefits another entity or the environment.
  • C. containsEcologicalTypes
    Indicates that one entity includes or encompasses specific ecological types or categories within it.
  • D. ecologicalStatus
    Indicates the condition or health of an ecosystem or environment, often in terms of its quality, integrity, or degree of disturbance.
  • E. ecologicalRelevance
    Indicates that one entity has significance, impact, or importance for the functioning, stability, or dynamics of another entity’s ecosystem or ecological context.
  • 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_69ca8484838c8190b2049199d22fef70 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9a366d3481908db62e476958eafe completed April 1, 2026, 10:20 p.m.
PD Predicate disambiguation batch_69ccd5a359788190b24f82399489f7fe completed April 1, 2026, 8:21 a.m.
PDg Predicate description generation batch_69ccd93fc45c8190a823305e461e581d completed April 1, 2026, 8:37 a.m.
Created at: March 30, 2026, 8:07 p.m.