Triple
T23971693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armistice of Pläswitz |
E604249
|
entity |
| Predicate | resumptionOfHostilities |
P121044
|
FINISHED |
| Object | 1813-08-10 |
—
|
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: 1813-08-10 | Statement: [Armistice of Pläswitz, resumptionOfHostilities, 1813-08-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resumptionOfHostilities Context triple: [Armistice of Pläswitz, resumptionOfHostilities, 1813-08-10]
-
A.
resumedArmedConflictWith
chosen
Indicates that a previously halted or paused armed conflict between two parties has started again.
-
B.
resumedCeasefire
Indicates that a previously halted ceasefire between parties has been restarted or put back into effect.
-
C.
endedCeasefire
Indicates that a previously established ceasefire between parties has been terminated or broken.
-
D.
ongoingConflict
Indicates a sustained, unresolved state of opposition or hostilities continuing between the involved entities.
-
E.
ceasefireResolution
Indicates a formal decision or agreement to halt hostilities or armed conflict between opposing parties, typically under specified terms and conditions.
- 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_69e29543019c8190872462e593cc50b4 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d1dc3f088190a55faf6f01ddf4bf |
completed | April 29, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:25 p.m.