Triple

T17628514
Position Surface form Disambiguated ID Type / Status
Subject Southern Ural Front E429911 entity
Predicate instanceOf P0 FINISHED
Object regional conflict zone C26725 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: regional conflict zone
Context triple: [Southern Ural Front, instanceOf, regional conflict zone]
  • A. conflict-affected area chosen
    A conflict-affected area is a geographic region where ongoing or recent armed violence, political instability, or social unrest significantly disrupts normal life, governance, and access to essential services.
  • B. geopolitical conflict
    A geopolitical conflict is a sustained struggle between nations or political entities driven by competing interests over territory, resources, ideology, or influence on the global stage.
  • C. military-controlled zone
    A military-controlled zone is a designated geographic area where military authorities exercise primary control over security, movement, and activities, often restricting civilian access and enforcing special regulations.
  • D. guerrilla conflict
    Guerrilla conflict is a form of irregular warfare in which small, mobile groups use hit-and-run tactics, ambushes, and sabotage to challenge a larger, conventionally organized force, often relying on local support and intimate knowledge of the terrain.
  • E. civil conflict
    Civil conflict is a sustained, organized struggle within a country between the state and one or more internal groups, or among such groups themselves, involving political, social, or economic grievances and often resulting in violence.
  • F. None of above.

Provenance (1 batch)

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_69d889e37f308190a6aa0a69daff86c7 completed April 10, 2026, 5:25 a.m.
Created at: April 10, 2026, 5:52 a.m.