Triple

T33666620
Position Surface form Disambiguated ID Type / Status
Subject Finnish defensive system on the eastern front E862509 entity
Predicate builtForConflictWith P14699 FINISHED
Object Red Army NE NERFINISHED

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: Red Army | Statement: [Finnish defensive system on the eastern front, builtForConflictWith, Red Army]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: builtForConflictWith
Context triple: [Finnish defensive system on the eastern front, builtForConflictWith, Red Army]
  • A. builtForConflict chosen
    Indicates that something is specifically designed or intended to function effectively in situations of conflict or confrontation.
  • B. conflictWith
    Indicates that two entities are in opposition or disagreement, such that their goals, actions, or states are incompatible or interfere with each other.
  • C. builtForConflictContext
    Indicates that something is designed, adapted, or intended specifically to function within or address a conflict situation or contentious context.
  • D. conflictIntroduced
    Indicates that a conflict has been newly created or brought into existence between the related entities.
  • E. formedInConflict
    Indicates that an entity came into existence as a direct result of, or during the course of, a specific conflict or war.
  • 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_69f34984c4008190bb82f33a7819da64 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6ffbad8848190867c2988c0ceb84f completed May 3, 2026, 7:56 a.m.
PD Predicate disambiguation batch_69f6fc5740fc81909774a4f65201a3ff completed May 3, 2026, 7:42 a.m.
Created at: May 1, 2026, 1:42 a.m.