Triple

T33711942
Position Surface form Disambiguated ID Type / Status
Subject Battle of Kłuszyn E863764 entity
Predicate casualtiesPolishLithuanian P23378 FINISHED
Object relatively light 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: relatively light | Statement: [Battle of Kłuszyn, casualtiesPolishLithuanian, relatively light]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: casualtiesPolishLithuanian
Context triple: [Battle of Kłuszyn, casualtiesPolishLithuanian, relatively light]
  • A. PolishCasualties chosen
    Indicates the number or extent of casualties suffered by Polish forces or population in a given conflict or event.
  • B. nativeCasualties
    Indicates that native or indigenous people suffered deaths or injuries as a result of a particular event, action, or conflict.
  • C. militaryCasualtiesSide
    Indicates the side or party in a conflict to which the recorded military casualties belong.
  • D. casualtiesCountry
    Indicates that the specified country is the one in which the recorded casualties (deaths or injuries) occurred or to which those casualties belong.
  • E. UnionCasualtiesKilledAndWounded
    Indicates the number of Union forces who were either killed or wounded as a result of a specific military engagement or event.
  • 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_69f3498844608190bb8f9b14908d2510 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6fabcd11c8190921eeaebd31a5a9d completed May 3, 2026, 7:35 a.m.
PD Predicate disambiguation batch_69f6f96dd4c8819093d6a7bd046a9ad5 completed May 3, 2026, 7:29 a.m.
Created at: May 1, 2026, 1:43 a.m.