Triple

T19555642
Position Surface form Disambiguated ID Type / Status
Subject Enguri Dam E489302 entity
Predicate nearSettlement P3883 FINISHED
Object Jvari 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: Jvari | Statement: [Enguri Dam, nearSettlement, Jvari]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jvari
Context triple: [Enguri Dam, nearSettlement, Jvari]
  • A. Jvari chosen
    Jvari is a town in northwestern Georgia known for its location near the Enguri River and the Enguri Dam in the Samegrelo-Zemo Svaneti region.
  • B. Dzvina
    Dzvina is the Belarusian name for the Daugava River, a major Eastern European river flowing through Russia, Belarus, and Latvia into the Baltic Sea.
  • C. Veleti
    The Veleti were a confederation of early medieval West Slavic tribes inhabiting the southern Baltic coast, known for their resistance to neighboring powers such as the early Polish state and the Holy Roman Empire.
  • D. Jvarboseli
    Jvarboseli is a small mountain village located in the remote Tusheti region of northeastern Georgia.
  • E. Vandjala
    Vandjala is a small village in northern Estonia located within Harku Parish in Harju County.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e8dc5d8c8190a6d7bd8864f43ca0 completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e63d335f888190abfc5ba974d3c65e completed April 20, 2026, 2:50 p.m.
Created at: April 10, 2026, 1:42 p.m.