Triple
T16758610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grigol Robakidze |
E407274
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Robakidze |
E407274
|
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: Robakidze | Statement: [Grigol Robakidze, familyName, Robakidze]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Robakidze Context triple: [Grigol Robakidze, familyName, Robakidze]
-
A.
Robakidze
chosen
Robakidze is a Georgian surname most notably borne by the writer and public figure Grigol Robakidze.
-
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.
Saakadze
Saakadze is a Georgian noble family name most famously associated with the 17th-century military commander Giorgi Saakadze.
-
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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3abea156c8190a5ee6d0028471810 |
completed | April 18, 2026, 4:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00a52b17b88190af24c04d16980c9f |
completed | May 10, 2026, 3:32 p.m. |
Created at: April 10, 2026, 5:21 a.m.