Triple
T35075498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cross River gorilla |
E1011999
|
entity |
| Predicate | IUCNRedListCategoryCode |
P1339
|
FINISHED |
| Object | CR |
—
|
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: CR | Statement: [Cross River gorilla, IUCNRedListCategoryCode, CR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IUCNRedListCategoryCode Context triple: [Cross River gorilla, IUCNRedListCategoryCode, CR]
-
A.
conservationStatus
chosen
Indicates the level of risk or protection category assigned to an entity, typically reflecting how threatened it is with extinction or decline.
-
B.
IUCNStatusSystem
Indicates the conservation status classification framework used to assign an IUCN threat category to a species or taxon.
-
C.
iucnRedListAuthority
Indicates the organization or authority responsible for assigning and maintaining the IUCN Red List conservation status for a taxon.
-
D.
wildlifeProtectionStatus
Indicates the level or type of legal or conservation protection currently applied to wildlife.
-
E.
speciesStatus
Indicates the conservation or population status assigned to a species, such as whether it is endangered, threatened, or of least concern.
- 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_69f76dd193108190af2528186f25b72a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7865b4684819093f95e659522b75e |
completed | May 3, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.