Triple

T481943
Position Surface form Disambiguated ID Type / Status
Subject German attack on Westerplatte E9186 entity
Predicate hasDefensivePosition P8412 FINISHED
Object fortified Polish depot and guardhouses 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: fortified Polish depot and guardhouses | Statement: [German attack on Westerplatte, hasDefensivePosition, fortified Polish depot and guardhouses]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDefensivePosition
Context triple: [German attack on Westerplatte, hasDefensivePosition, fortified Polish depot and guardhouses]
  • A. defensiveRole
    Indicates that an entity serves a protective or guarding function in relation to another entity or context.
  • B. defensiveStructure chosen
    Indicates a relationship where one entity functions as a structure built or used to protect, defend, or fortify another entity or area.
  • C. defensivePlan
    Indicates a relationship where an entity formulates or adopts a strategy specifically intended to protect against threats, attacks, or other adverse actions.
  • D. hasDefenderStrength
    Indicates that an entity possesses a certain level or measure of defensive capability or protective power.
  • E. defensiveTask
    Indicates a task in which an entity protects, guards, or defends another entity or resource from potential threats or harm.
  • 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_69a2e7ff81708190b0507a24a997232c completed Feb. 28, 2026, 1:05 p.m.
NER Named-entity recognition batch_69a2f05a7f6c819082b4a5a3e69468a6 completed Feb. 28, 2026, 1:40 p.m.
PD Predicate disambiguation batch_69a2edf321288190b5d560f75782c2cb completed Feb. 28, 2026, 1:30 p.m.
Created at: Feb. 28, 2026, 1:12 p.m.