Triple

T13333657
Position Surface form Disambiguated ID Type / Status
Subject იევლახი E317632 entity
Predicate hasNearbyRiver P8567 FINISHED
Object კურა E82236 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: კურა | Statement: [იევლახი, hasNearbyRiver, კურა]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: კურა
Context triple: [იევლახი, hasNearbyRiver, კურა]
  • A. Kur
    Kur is the ancient Mesopotamian underworld, a dark subterranean realm of the dead ruled by the goddess Ereshkigal.
  • B. Kurâ
    Kurâ is an alternative name for the Bakairi language, an indigenous Cariban language spoken by the Bakairi people of Brazil.
  • C. Kuresa
    Kuresa, also known by the honorific Koorathazhwan, was a prominent 11th-century Sri Vaishnava scholar and chief disciple of the theologian Ramanuja.
  • D. Curan
    Curan is a small rural commune in the Aveyron department of southern France, known for its proximity to the large artificial Lac de Pareloup and its agricultural landscape.
  • E. Kür chosen
    Kür is the Azerbaijani name for the Kura River, a major waterway flowing through Turkey, Georgia, and Azerbaijan into the Caspian Sea.
  • 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_69d806b4d62c81908d4ced1665414be5 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d99cff44e08190b9583baf0b626e42 completed April 11, 2026, 12:59 a.m.
NED1 Entity disambiguation (via context triple) batch_69f71f36e4cc819093007404ceb5da31 completed May 3, 2026, 10:11 a.m.
Created at: April 9, 2026, 9:30 p.m.