Triple
T16795666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arctogadus glacialis |
E408223
|
entity |
| Predicate | threatFrom |
P1358
|
FINISHED |
| Object | climate change |
—
|
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: climate change | Statement: [Arctogadus glacialis, threatFrom, climate change]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threatFrom Context triple: [Arctogadus glacialis, threatFrom, climate change]
-
A.
threatType
Indicates the specific category or nature of a threat that one entity poses or represents in relation to another.
-
B.
threat
chosen
Indicates a relationship where one entity expresses or poses potential harm, danger, or negative consequences toward another entity.
-
C.
threatContained
Indicates that an identified threat has been successfully neutralized, controlled, or otherwise prevented from causing further harm or escalation.
-
D.
threatStatus
Indicates the level or category of risk or danger posed by one entity to another or to a defined system or environment.
-
E.
threatCategory
Indicates the classification of a threat according to its type, severity, or nature within a defined risk or security framework.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2a96d888190a9876c3784bb7f95 |
completed | April 18, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.