Triple

T26060421
Position Surface form Disambiguated ID Type / Status
Subject Moscow Armistice with Finland E657241 entity
Predicate requiredExpulsionOf P174231 FINISHED
Object German forces from Finland 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: German forces from Finland | Statement: [Moscow Armistice with Finland, requiredExpulsionOf, German forces from Finland]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: requiredExpulsionOf
Context triple: [Moscow Armistice with Finland, requiredExpulsionOf, German forces from Finland]
  • A. requestedExpulsionOf
    Indicates that one entity formally asked an authority or relevant body to expel or remove another entity from a group, place, or organization.
  • B. expulsionReason
    Indicates the cause or justification for which an entity was expelled from a group, place, or institution.
  • C. expulsionEvent
    Indicates an event in which an entity is formally forced to leave or is removed from a place, group, or institution.
  • D. expelledTo
    Indicates that an entity has been formally forced to leave one place, organization, or group and sent to another specified location.
  • E. expulsionStart
    Indicates the point in time when an expulsion process or event begins.
  • F. None of above. chosen

Provenance (4 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_69f6bcc425588190afd0dceba43ed79f completed May 3, 2026, 3:11 a.m.
PD Predicate disambiguation batch_69f6ba6b1e6c8190adf9d6a257e0b744 completed May 3, 2026, 3 a.m.
PDg Predicate description generation batch_69f6bbf5a8288190ae170bcbe8ab65cf completed May 3, 2026, 3:07 a.m.
Created at: April 26, 2026, 7:17 p.m.