Triple

T14973814
Position Surface form Disambiguated ID Type / Status
Subject Mamia I Gurieli E373391 entity
Predicate hasHonorific P2097 FINISHED
Object Gurieli E1130339 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: Gurieli | Statement: [Mamia I Gurieli, hasHonorific, Gurieli]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gurieli
Context triple: [Mamia I Gurieli, hasHonorific, Gurieli]
  • A. Gurieli chosen
    Gurieli was a hereditary princely title held by a noble family that ruled the region of Guria in western Georgia.
  • B. Arsukidze
    Arsukidze was a medieval Georgian architect renowned as the master builder of the Svetitskhoveli Cathedral in Mtskheta.
  • C. Jorjadze
    Jorjadze is a Georgian noble family name historically associated with aristocracy, landownership, and cultural influence in Georgia.
  • D. Tsakhuri
    Tsakhuri is an alternative name for the Tsakhur language, a Northeast Caucasian language spoken primarily in parts of Azerbaijan and Dagestan.
  • E. Tsereteli
    Tsereteli is a Georgian noble family name historically associated with prominent political, cultural, and public figures from Georgia.
  • 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_69d85ccbbcd48190acb56e7cf104d8ad completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded6e767608190940eb6f16ea97451 completed April 15, 2026, 12:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69fe9692e4fc8190a1194a41fc8a832c completed May 9, 2026, 2:06 a.m.
Created at: April 10, 2026, 2:50 a.m.