Triple
T501933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Munich Agreement |
E10419
|
entity |
| Predicate | aimedToPrevent |
P9207
|
FINISHED |
| Object | outbreak of war in Europe |
—
|
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: outbreak of war in Europe | Statement: [Munich Agreement, aimedToPrevent, outbreak of war in Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimedToPrevent Context triple: [Munich Agreement, aimedToPrevent, outbreak of war in Europe]
-
A.
prevented
Indicates that one entity stopped, hindered, or made it impossible for another entity or event to occur or proceed.
-
B.
aimsToProtect
chosen
Indicates an intention or purpose to safeguard or defend one entity, value, or condition from harm, risk, or undesirable outcomes.
-
C.
aimedToImplement
Indicates that an entity had the intention or plan to carry out, realize, or put another entity (such as a policy, idea, or system) into effect.
-
D.
protectionObjective
Indicates that one entity has the goal or purpose of safeguarding, defending, or preserving another entity or its interests.
-
E.
prohibits
Indicates that one entity forbids or disallows another entity from performing a specific action or being in a certain state.
- 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_69a2e848adf881908e5e04f7af030093 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1339748819089f89691a1698dd9 |
completed | Feb. 28, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69a2edfbb7e0819092cf29c2c68fe8fb |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.