Triple
T501959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Munich Agreement |
E10419
|
entity |
| Predicate | legalStatusAfterWWII |
P4701
|
FINISHED |
| Object | repudiated |
—
|
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: repudiated | Statement: [Munich Agreement, legalStatusAfterWWII, repudiated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusAfterWWII Context triple: [Munich Agreement, legalStatusAfterWWII, repudiated]
-
A.
statusAfterWWII
Indicates the condition, role, or classification an entity had following the end of World War II.
-
B.
legalStatusAfterWar
chosen
Indicates the legal condition or classification assigned to an entity as a consequence of, or following the conclusion of, a war or armed conflict.
-
C.
postWarOccupation
Indicates that one entity occupied, administered, or controlled another entity or territory in the period following a war.
-
D.
postwarOutcome
Indicates the result or consequences that follow for a party or situation after a war has ended.
-
E.
sideInWorldWarII
Indicates that an entity was aligned with or participated on a particular side during World War II.
- 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.