Triple

T35220175
Position Surface form Disambiguated ID Type / Status
Subject Kodori River E1016928 entity
Predicate hasNameInAbkhaz P67422 FINISHED
Object Кодор 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: Кодор | Statement: [Kodori River, hasNameInAbkhaz, Кодор]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNameInAbkhaz
Context triple: [Kodori River, hasNameInAbkhaz, Кодор]
  • A. nameInAbkhaz chosen
    Indicates that an entity’s name is given in the Abkhaz language.
  • B. hasNameInAdyghe
    Indicates that an entity is known or referred to by a specific name in the Adyghe language.
  • C. hasNameInAzerbaijani
    Indicates that an entity is known by a specific name when expressed in the Azerbaijani language.
  • D. hasNameInTigrinya
    Indicates that an entity is associated with a specific name expressed in the Tigrinya language.
  • E. hasNameInSakha
    Indicates that an entity is associated with a specific name expressed in the Sakha (Yakut) language.
  • 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_69f76de072908190ab65038a8a7b6a79 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69ff397e19a88190a945b826159f5290 completed May 9, 2026, 1:41 p.m.
PD Predicate disambiguation batch_69ff392400d0819088d30d08d4a774bd completed May 9, 2026, 1:39 p.m.
Created at: May 3, 2026, 4:02 p.m.