Triple
T16988505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copernicus Emergency Management Service |
E412130
|
entity |
| Predicate | supportsInternationalFramework |
P125494
|
FINISHED |
| Object | Sendai Framework for Disaster Risk Reduction |
E105480
|
NE FINISHED |
How this triple was built (3 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: Sendai Framework for Disaster Risk Reduction | Statement: [Copernicus Emergency Management Service, supportsInternationalFramework, Sendai Framework for Disaster Risk Reduction]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sendai Framework for Disaster Risk Reduction Context triple: [Copernicus Emergency Management Service, supportsInternationalFramework, Sendai Framework for Disaster Risk Reduction]
-
A.
Sendai Framework for Disaster Risk Reduction 2015–2030
chosen
The Sendai Framework for Disaster Risk Reduction 2015–2030 is a global UN-endorsed agreement that sets priorities and targets for reducing disaster risk and enhancing resilience to natural and human-made hazards worldwide.
-
B.
Global Platform for Disaster Risk Reduction
The Global Platform for Disaster Risk Reduction is a biennial multi-stakeholder forum that serves as the main global venue for assessing progress, sharing knowledge, and setting priorities in reducing disaster risk and building resilience.
-
C.
Hyogo Framework for Action 2005–2015
The Hyogo Framework for Action 2005–2015 was a global blueprint adopted by UN member states to systematically reduce disaster risks and build the resilience of nations and communities.
-
D.
Regional Platforms for Disaster Risk Reduction
Regional Platforms for Disaster Risk Reduction are UN-supported multi-stakeholder forums in different world regions that coordinate and advance policies, strategies, and cooperation to reduce disaster risks and build resilience.
-
E.
Philippine disaster risk reduction system
The Philippine disaster risk reduction system is the country’s coordinated framework of government agencies, laws, and programs designed to prevent, prepare for, respond to, and recover from natural and human-induced disasters.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsInternationalFramework Context triple: [Copernicus Emergency Management Service, supportsInternationalFramework, Sendai Framework for Disaster Risk Reduction]
-
A.
supportsInternationalization
Indicates that an entity provides functionality or features that enable use across multiple languages, locales, or regional formats.
-
B.
supportsPrinciple
Indicates that one entity endorses, upholds, or actively backs a particular principle or doctrine.
-
C.
supportsCountry
Indicates that one entity provides assistance, endorsement, or backing to a specific country.
-
D.
supportsUse
Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
-
E.
isInternational
Indicates that something has a connection to, involves, or extends across more than one country.
- F. None of above. chosen
Provenance (5 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d27dca248190a9b73b16439d5631 |
completed | April 18, 2026, 6:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00dc12e308819093e7f8933cdd6ba9 |
completed | May 10, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69e3753f93c88190808fec5692f66699 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:32 a.m.