Triple

T1862772
Position Surface form Disambiguated ID Type / Status
Subject Third Silesian War E34852 entity
Predicate statusOfSilesiaAfterWar P4701 FINISHED
Object remained under Prussian control 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: remained under Prussian control | Statement: [Third Silesian War, statusOfSilesiaAfterWar, remained under Prussian control]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: statusOfSilesiaAfterWar
Context triple: [Third Silesian War, statusOfSilesiaAfterWar, remained under Prussian control]
  • A. statusInCommunistPoland
    Indicates the social, legal, or political standing an entity held within the societal system of communist-era Poland.
  • 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. statusAfterWWII
    Indicates the condition, role, or classification an entity had following the end of World War II.
  • D. PolishCasualties
    Indicates the number or extent of casualties suffered by Polish forces or population in a given conflict or event.
  • E. postWarOccupation
    Indicates that one entity occupied, administered, or controlled another entity or territory in the period following a war.
  • 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_69a88600b2f88190bc09303e68ab517e completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69abb16c09e48190a345c95eab59fd87 completed March 7, 2026, 5:02 a.m.
PD Predicate disambiguation batch_69abafe02c3c819093a4744b476106ca completed March 7, 2026, 4:56 a.m.
Created at: March 4, 2026, 7:34 p.m.