Triple

T30134395
Position Surface form Disambiguated ID Type / Status
Subject 62nd Army E765944 entity
Predicate frontLinePosition P117051 FINISHED
Object defended west bank of the Volga at Stalingrad 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: defended west bank of the Volga at Stalingrad | Statement: [62nd Army, frontLinePosition, defended west bank of the Volga at Stalingrad]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: frontLinePosition
Context triple: [62nd Army, frontLinePosition, defended west bank of the Volga at Stalingrad]
  • A. frontLine
    Indicates that an entity is positioned at or associated with the foremost or primary line of engagement, activity, or defense relative to others.
  • B. frontLineBetween
    Indicates that a boundary or line of direct confrontation exists separating two opposing sides or regions.
  • C. frontLineNear
    Indicates that one entity is located close to the primary boundary or front line associated with another entity.
  • D. frontLineDuring chosen
    Indicates that an entity is positioned at or serves on the front line during a specified time or event.
  • E. frontLineDirection
    Indicates the primary orientation or bearing in which the front line of a conflict, formation, or boundary is facing or advancing.
  • 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_69f22477d1a081908df2b7e6ed16859d completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f67e4b8e4c8190ac23fef21a55d5f0 completed May 2, 2026, 10:44 p.m.
PD Predicate disambiguation batch_69f678ce54b081908c26edfd49e39c60 completed May 2, 2026, 10:21 p.m.
Created at: April 29, 2026, 7:16 p.m.