Triple

T34169942
Position Surface form Disambiguated ID Type / Status
Subject Scleropages E876515 entity
Predicate conservationStatusOfSomeSpecies P141134 FINISHED
Object endangered 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: endangered | Statement: [Scleropages, conservationStatusOfSomeSpecies, endangered]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: conservationStatusOfSomeSpecies
Context triple: [Scleropages, conservationStatusOfSomeSpecies, endangered]
  • A. conservationStatus
    Indicates the level of risk or protection category assigned to an entity, typically reflecting how threatened it is with extinction or decline.
  • B. subjectSpeciesStatus
    Indicates the conservation or biological status assigned to the subject species (e.g., endangered, native, invasive, protected).
  • C. speciesStatus chosen
    Indicates the conservation or population status assigned to a species, such as whether it is endangered, threatened, or of least concern.
  • D. hasConservationConcernIn
    Indicates that an entity is subject to a specified conservation concern status within a particular geographic area or jurisdiction.
  • E. areEndangeredIn
    Indicates that the entities are classified as endangered within a specified geographic area or jurisdiction.
  • 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_69f349ad97ac8190bf1f17417c970e64 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f7a225a77c81908f8953ccfeb14336 completed May 3, 2026, 7:29 p.m.
PD Predicate disambiguation batch_69f7a06d4f108190bae3ab9ae431d2c7 completed May 3, 2026, 7:22 p.m.
Created at: May 1, 2026, 1:54 a.m.