Triple
T8652622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sockeye salmon |
E205134
|
entity |
| Predicate | hasIUCNStatus |
P1339
|
FINISHED |
| Object | Least Concern (global) |
—
|
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: Least Concern (global) | Statement: [Sockeye salmon, hasIUCNStatus, Least Concern (global)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIUCNStatus Context triple: [Sockeye salmon, hasIUCNStatus, Least Concern (global)]
-
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.
wildlifeProtectionStatus
Indicates the level or type of legal or conservation protection currently applied to wildlife.
-
D.
previousIucnStatus
Indicates the conservation status an entity held in the IUCN Red List before its current or most recent assessment.
-
E.
stateOfConservation
Indicates the condition or preservation status of an entity, typically in terms of how intact, degraded, or at risk it is.
- 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_69ca834e56848190abb0eeaec9dedd32 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc484051b48190b1d0cc63426c204d |
completed | March 31, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69cc45619460819091e83ffdec99c865 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:29 p.m.