Triple

T28438710
Position Surface form Disambiguated ID Type / Status
Subject Caucasus front E715644 entity
Predicate theaterOfOperationsFor P710 FINISHED
Object Russian Caucasus 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: Russian Caucasus Army | Statement: [Caucasus front, theaterOfOperationsFor, Russian Caucasus Army]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: theaterOfOperationsFor
Context triple: [Caucasus front, theaterOfOperationsFor, Russian Caucasus Army]
  • A. theaterOfWar
    Indicates that a specified location or region is the primary area where a particular conflict, war, or military operation takes place.
  • B. militaryTheater chosen
    Indicates that an entity is a geographic or operational area where military operations or campaigns are conducted.
  • C. fieldOfOperation
    Indicates the domain, area, or scope within which an entity operates or carries out its primary activities.
  • D. militaryTheaterReportedOn
    Indicates that a report or account has been made about a particular military theater or area of operations.
  • E. militaryTheaterCovered
    Indicates that a specified military theater or area of operations falls within the geographic or operational scope covered by another entity (such as a plan, command, or agreement).
  • 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_69efd6b44550819094ae991b553d9fc3 completed April 27, 2026, 9:35 p.m.
NER Named-entity recognition batch_69f64e3bfcf481909759bc5f2a077fde completed May 2, 2026, 7:19 p.m.
PD Predicate disambiguation batch_69f64caede108190a35cc7cbfead866f completed May 2, 2026, 7:12 p.m.
Created at: April 28, 2026, 1:44 a.m.