Triple

T38081717
Position Surface form Disambiguated ID Type / Status
Subject 2008 Battle of the Kodori Valley E950868 entity
Predicate statusOfAreaAfterBattle P109227 FINISHED
Object full control by Abkhaz and Russian-aligned forces 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: full control by Abkhaz and Russian-aligned forces | Statement: [2008 Battle of the Kodori Valley, statusOfAreaAfterBattle, full control by Abkhaz and Russian-aligned forces]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: statusOfAreaAfterBattle
Context triple: [2008 Battle of the Kodori Valley, statusOfAreaAfterBattle, full control by Abkhaz and Russian-aligned forces]
  • A. statusOfAreaBeforeBattle
    Indicates the condition or situation of a specific area immediately prior to a battle taking place.
  • B. statusAfterBattle chosen
    Indicates the condition or state of an entity following the completion of a battle or combat encounter.
  • C. statusAfterBattleForAzeroth
    Indicates the condition or state of an entity following the events of the Battle for Azeroth.
  • D. statusOfCityBeforeBattle
    Indicates the condition or situation a city was in immediately prior to a specific battle.
  • E. statusAfterAttack
    Indicates the resulting condition or state of an entity after an attack has occurred.
  • 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_69f76f03a3608190a73fd6df87c792a8 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_6a000014497c819088d5cda3977522dd completed May 10, 2026, 3:48 a.m.
PD Predicate disambiguation batch_69ffff9a52b08190be1024e0fb6fe661 completed May 10, 2026, 3:46 a.m.
Created at: May 3, 2026, 4:21 p.m.