Triple

T29082843
Position Surface form Disambiguated ID Type / Status
Subject Zen-Whoberian E734023 entity
Predicate causeOfNearExtinction P6998 FINISHED
Object genocide by Badoon (in some continuities) 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: genocide by Badoon (in some continuities) | Statement: [Zen-Whoberian, causeOfNearExtinction, genocide by Badoon (in some continuities)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: causeOfNearExtinction
Context triple: [Zen-Whoberian, causeOfNearExtinction, genocide by Badoon (in some continuities)]
  • A. extinctionReason chosen
    Indicates the cause or factor responsible for an entity’s extinction.
  • B. wasOnceNearExtinction
    Indicates that the entity’s population or existence was at one time so low or threatened that it was in serious danger of disappearing entirely.
  • C. impactOfExtinction
    Indicates the consequences or effects that the extinction of an entity has on other entities, systems, or conditions.
  • D. massExtinctionConsequence
    Indicates that an event or factor results in, contributes to, or is a direct outcome of a mass extinction event.
  • E. creationCanBecomeExtinct
    Indicates that something which has been created is capable of ceasing to exist or becoming extinct.
  • 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_69f05b0c0f28819086eae6e84f2ae472 completed April 28, 2026, 7 a.m.
NER Named-entity recognition batch_69f71422adac8190a5ceb32dcf820833 completed May 3, 2026, 9:23 a.m.
PD Predicate disambiguation batch_69f712764d2c819081b64b27e5de4a13 completed May 3, 2026, 9:16 a.m.
Created at: April 28, 2026, 10:57 a.m.