Triple
T16988480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copernicus Emergency Management Service |
E412130
|
entity |
| Predicate | supportsHazardType |
P1950
|
FINISHED |
| Object | floods |
—
|
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: floods | Statement: [Copernicus Emergency Management Service, supportsHazardType, floods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsHazardType Context triple: [Copernicus Emergency Management Service, supportsHazardType, floods]
-
A.
hasHazardLevel
Indicates that an entity is associated with a specified degree or category of risk or danger.
-
B.
hazardType
chosen
Indicates the specific kind or category of hazard associated with an entity or situation.
-
C.
hazmatSupport
Indicates that one entity provides hazardous materials (hazmat) response or support services to another entity or situation.
-
D.
monitorsHazardType
Indicates that an entity observes, tracks, or keeps watch over a specified type or category of hazard.
-
E.
hasNotableHazard
Indicates that an entity is associated with a significant risk, danger, or harmful condition that is noteworthy or exceptional.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d27dca248190a9b73b16439d5631 |
completed | April 18, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.