Triple
T26060409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow Armistice with Finland |
E657241
|
entity |
| Predicate | warReparationsPaidTo |
P118814
|
FINISHED |
| Object | Soviet Union |
—
|
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: Soviet Union | Statement: [Moscow Armistice with Finland, warReparationsPaidTo, Soviet Union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warReparationsPaidTo Context triple: [Moscow Armistice with Finland, warReparationsPaidTo, Soviet Union]
-
A.
transferredAsWarReparationsTo
chosen
Indicates that something was moved from one party to another specifically as compensation or payment imposed after a war.
-
B.
imposedWarIndemnityOn
Indicates that one party required another party to pay financial compensation as a penalty or reparation following a conflict or war.
-
C.
warIndemnityAmount
Indicates the amount of financial compensation required or paid as indemnity as a result of a war or armed conflict.
-
D.
MunichAgreementSignatory
Indicates that an entity was a formal signatory to the Munich Agreement.
-
E.
remilitarizedBy
Indicates that a previously demilitarized area, zone, or entity has been restored to military status or armed forces presence by a specified actor.
- 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_69ee5bbd788481909e22bd7153d0c037 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60691a4c081909a2589d00b68838d |
completed | May 2, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 7:17 p.m.