Triple

T777248
Position Surface form Disambiguated ID Type / Status
Subject Imereti E16413 entity
Predicate bordersRegion P224 FINISHED
Object Guria E17206 NE 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: Guria | Statement: [Imereti, bordersRegion, Guria]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Guria
Context triple: [Imereti, bordersRegion, Guria]
  • A. Guria chosen
    Guria is a historical region in western Georgia known for its Black Sea coastline, rich folk traditions, and distinctive polyphonic singing.
  • B. Samegrelo
    Samegrelo is a historic region in western Georgia known for its distinct Mingrelian culture, language, and cuisine.
  • C. Svaneti
    Svaneti is a remote mountainous region in northwestern Georgia, renowned for its medieval stone tower houses, unique Svan culture and language, and dramatic Caucasus landscapes.
  • D. Ossetia
    Ossetia is a historical and cultural region in the central Caucasus, divided between Russia and Georgia, known as the homeland of the Ossetian people.
  • E. Kartli
    Kartli is a historic central region of Georgia that has long been a political and cultural heartland for the Georgian people.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69a4936ad1fc81908f190208059ccf78 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a74da7648190adfad56717d564df completed March 1, 2026, 8:53 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac118d9b408190b1dd9540386406f2 completed March 7, 2026, 11:52 a.m.
Created at: March 1, 2026, 7:37 p.m.