Triple

T10948960
Position Surface form Disambiguated ID Type / Status
Subject 10 Armia (Niemcy) E258673 entity
Predicate funkcja P81043 FINISHED
Object prowadzenie działań ofensywnych przeciwko Polsce 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: prowadzenie działań ofensywnych przeciwko Polsce | Statement: [10 Armia (Niemcy), funkcja, prowadzenie działań ofensywnych przeciwko Polsce]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: funkcja
Context triple: [10 Armia (Niemcy), funkcja, prowadzenie działań ofensywnych przeciwko Polsce]
  • A. functie chosen
    Indicates that one entity serves as a function, role, or operational purpose in relation to another entity.
  • B. 기능
    Indicates that an entity has a particular function, role, or operational capability.
  • C. formFunction
    Indicates that one entity’s physical form, structure, or configuration determines or enables the function or role performed by another (or by itself).
  • D. notFunction
    Indicates that the specified entity does not serve as a function or is not used in a functional role within the given context.
  • E. functionInWork
    Indicates that a particular function, role, or operation is performed, utilized, or occurs within the context of a specific work or creation.
  • 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_69d6aa88500c819097d7032ca578e74f completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d770ec7028819084f5ce2035a128e4 completed April 9, 2026, 9:27 a.m.
PD Predicate disambiguation batch_69d72e816a98819096d6c10dfb88a66a completed April 9, 2026, 4:43 a.m.
Created at: April 8, 2026, 9:23 p.m.