Triple

T32184258
Position Surface form Disambiguated ID Type / Status
Subject Nednhi Ndé E822062 entity
Predicate isEndangeredAsDistinctGroup P173292 FINISHED
Object true 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: true | Statement: [Nednhi Ndé, isEndangeredAsDistinctGroup, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isEndangeredAsDistinctGroup
Context triple: [Nednhi Ndé, isEndangeredAsDistinctGroup, true]
  • A. areEndangeredIn
    Indicates that the entities are classified as endangered within a specified geographic area or jurisdiction.
  • B. areEndangeredOrVulnerable
    Indicates that the entities are classified as being at risk of extinction, either endangered or vulnerable, according to conservation status criteria.
  • C. isEndangeredDueTo
    Indicates that an entity is endangered as a result of the specific cause or factor represented by the related entity.
  • D. conservationStatus
    Indicates the level of risk or protection category assigned to an entity, typically reflecting how threatened it is with extinction or decline.
  • E. areEndangeredInPart
    Indicates that an entity is endangered only in certain regions or parts of its overall range, rather than throughout its entire distribution.
  • 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_69f3490755288190aee11740a34862f9 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6bab75a948190a531ac204aee4fca completed May 3, 2026, 3:02 a.m.
PD Predicate disambiguation batch_69f6b3aa892481908d29283a074e6722 completed May 3, 2026, 2:32 a.m.
PDg Predicate description generation batch_69f6b42902a081909126c7322858a2b3 completed May 3, 2026, 2:34 a.m.
Created at: May 1, 2026, 12:35 a.m.