Triple
T2378706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boé Declaration on Regional Security |
E46260
|
entity |
| Predicate | recognizesThreat |
P38345
|
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: [Boé Declaration on Regional Security, recognizesThreat, climate change]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizesThreat Context triple: [Boé Declaration on Regional Security, recognizesThreat, climate change]
-
A.
threatTypeAddressed
Indicates that a given action, measure, or entity is specifically intended to counter or mitigate a particular type of threat.
-
B.
threatCategory
Indicates the classification of a threat according to its type, severity, or nature within a defined risk or security framework.
-
C.
historicalThreat
Indicates that one entity posed a significant threat to another in the past, but is not necessarily a current or ongoing danger.
-
D.
threatTypeEngaged
Indicates that an entity has actively engaged with or responded to a specific type of threat.
-
E.
threatStatus
Indicates the level or category of risk or danger posed by one entity to another or to a defined system or environment.
- 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_69a88a1554a48190a0180682bcf099be |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abc7974aa481908799ef2f854d1c9d |
completed | March 7, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69abc59f73f08190924a36d7d475d8f4 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abc6f4245881909282b3184a288e2a |
completed | March 7, 2026, 6:34 a.m. |
Created at: March 4, 2026, 7:57 p.m.