Triple

T316867
Position Surface form Disambiguated ID Type / Status
Subject Hungarian 2nd Army E7725 entity
Predicate defensiveTask P11967 FINISHED
Object hold Don River line against Soviet attacks 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: hold Don River line against Soviet attacks | Statement: [Hungarian 2nd Army, defensiveTask, hold Don River line against Soviet attacks]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: defensiveTask
Context triple: [Hungarian 2nd Army, defensiveTask, hold Don River line against Soviet attacks]
  • A. defensivePlan
    Indicates a relationship where an entity formulates or adopts a strategy specifically intended to protect against threats, attacks, or other adverse actions.
  • B. defensiveStructure
    Indicates a relationship where one entity functions as a structure built or used to protect, defend, or fortify another entity or area.
  • C. defends
    Indicates that one entity protects or supports another entity against attack, criticism, or harm.
  • D. defender
    Indicates a relationship where one entity protects, guards, or supports another entity against threats, attacks, or criticism.
  • E. defenseResult
    Indicates the outcome or consequence of a defensive action or strategy in response to an attack or threat.
  • 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_69a2e7e7af7881908890039d6be4e9b8 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2ea65ca7081908093e6aaaf2d34f7 completed Feb. 28, 2026, 1:15 p.m.
PD Predicate disambiguation batch_69a2e943f12c8190883854aeed974260 completed Feb. 28, 2026, 1:10 p.m.
PDg Predicate description generation batch_69a2ea08878c8190a5e8a90f620a3888 completed Feb. 28, 2026, 1:13 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.