Triple
T36679771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2021 European floods |
E905644
|
entity |
| Predicate | promptedEUMechanism |
P134741
|
FINISHED |
| Object | EU Civil Protection Mechanism |
—
|
NE NERFINISHED |
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: EU Civil Protection Mechanism | Statement: [2021 European floods, promptedEUMechanism, EU Civil Protection Mechanism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promptedEUMechanism Context triple: [2021 European floods, promptedEUMechanism, EU Civil Protection Mechanism]
-
A.
promptedAction
chosen
Indicates that one entity initiates or triggers another entity to perform a specific action.
-
B.
promptedDemandFor
Indicates that one entity’s action or occurrence caused an increase in demand for another entity.
-
C.
supportsPrompting
Indicates that one entity enables or is compatible with interactive prompting behavior for another entity.
-
D.
conformanceMechanism
Indicates the method, process, or mechanism by which something complies with or adheres to a specified standard, rule, or requirement.
-
E.
settlementEncouragedBy
Indicates that the establishment or growth of a settlement is promoted, supported, or stimulated by a particular factor, agent, or condition.
- 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_69f76e7011dc819082b324f18b756a1b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.