Triple

T12730993
Position Surface form Disambiguated ID Type / Status
Subject Nikolai Tsiskaridze E304234 entity
Predicate familyName P18 FINISHED
Object Tsiskaridze E304234 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: Tsiskaridze | Statement: [Nikolai Tsiskaridze, familyName, Tsiskaridze]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tsiskaridze
Context triple: [Nikolai Tsiskaridze, familyName, Tsiskaridze]
  • A. Arsukidze
    Arsukidze was a medieval Georgian architect renowned as the master builder of the Svetitskhoveli Cathedral in Mtskheta.
  • B. Robakidze
    Robakidze is a Georgian surname most notably borne by the writer and public figure Grigol Robakidze.
  • C. Javakhishvili
    Javakhishvili is a Georgian surname most notably associated with prominent figures such as writer Mikheil Javakhishvili.
  • D. Nikolai Tsiskaridze chosen
    Nikolai Tsiskaridze is a celebrated Georgian-Russian ballet dancer and teacher, renowned as one of the leading male stars of late 20th- and early 21st-century Russian ballet.
  • E. Avel Yenukidze
    Avel Yenukidze was a Georgian Bolshevik revolutionary and Soviet statesman who played a key role in the early Soviet government and was later a victim of Stalin’s Great Purge.
  • 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_69d7bdf1426c8190a4402e1c4cdec33a completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96467a2248190aff1ebb5db84b3c6 completed April 10, 2026, 8:58 p.m.
NED1 Entity disambiguation (via context triple) batch_69f69b8c84308190b57d3b5b04bb4a78 completed May 3, 2026, 12:49 a.m.
Created at: April 9, 2026, 5:25 p.m.