Triple

T8921129
Position Surface form Disambiguated ID Type / Status
Subject Chernobyl Exclusion Zone E212416 entity
Predicate floraFaunaStatus P79076 FINISHED
Object significant wildlife presence 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: significant wildlife presence | Statement: [Chernobyl Exclusion Zone, floraFaunaStatus, significant wildlife presence]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: floraFaunaStatus
Context triple: [Chernobyl Exclusion Zone, floraFaunaStatus, significant wildlife presence]
  • A. wildlifeProtectionStatus
    Indicates the level or type of legal or conservation protection currently applied to wildlife.
  • B. biodiversityStatus
    Indicates the current condition or level of biological diversity associated with an entity, often in terms of richness, health, or conservation concern.
  • C. conservationStatus
    Indicates the level of risk or protection category assigned to an entity, typically reflecting how threatened it is with extinction or decline.
  • D. subjectSpeciesStatus
    Indicates the conservation or biological status assigned to the subject species (e.g., endangered, native, invasive, protected).
  • E. hasWildlifeStatus chosen
    Indicates the conservation or protection status assigned to wildlife associated with an entity.
  • 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_69ca839481d48190b42b037e0d0f636c completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc665024f081909515e02e5f5b2221 completed April 1, 2026, 12:26 a.m.
PD Predicate disambiguation batch_69cc5ed0ef3c81908cc69eac852ee12a completed March 31, 2026, 11:54 p.m.
Created at: March 30, 2026, 6:56 p.m.