Triple

T33711937
Position Surface form Disambiguated ID Type / Status
Subject Battle of Kłuszyn E863764 entity
Predicate strengthPolishLithuanian P177228 FINISHED
Object approximately 6,000–7,000 troops 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: approximately 6,000–7,000 troops | Statement: [Battle of Kłuszyn, strengthPolishLithuanian, approximately 6,000–7,000 troops]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: strengthPolishLithuanian
Context triple: [Battle of Kłuszyn, strengthPolishLithuanian, approximately 6,000–7,000 troops]
  • A. PolishObjective
    Indicates that an entity is the target or goal of a polishing action or process.
  • B. SaxonPolishStrength
    Indicates a relationship where the strength or power dynamics between Saxon and Polish entities are being compared, measured, or characterized.
  • C. isPolish
    Indicates that an entity has the property of being Polish, typically in terms of nationality, origin, or cultural affiliation.
  • D. polishUnit
    Indicates that one entity performs the action of polishing or refining another entity, typically improving its surface, appearance, or quality.
  • E. meaningInPolish
    Indicates that one entity expresses the meaning or translation of another entity in the Polish language.
  • 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_69f3498844608190bb8f9b14908d2510 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6fae2a7a8819099945d1706a94bfd completed May 3, 2026, 7:36 a.m.
PD Predicate disambiguation batch_69f6f96dd4c8819093d6a7bd046a9ad5 completed May 3, 2026, 7:29 a.m.
PDg Predicate description generation batch_69f6fa335b908190a20d92d5396203b5 completed May 3, 2026, 7:33 a.m.
Created at: May 1, 2026, 1:43 a.m.