Triple
T15848096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giorgi Saakadze |
E384264
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Giorgi |
E762095
|
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: Giorgi | Statement: [Giorgi Saakadze, givenName, Giorgi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Giorgi Context triple: [Giorgi Saakadze, givenName, Giorgi]
-
A.
Giorgi
Giorgi is an Italian surname borne by various individuals, including those with the given name Francesco.
-
B.
Giorgi
chosen
Giorgi is the Georgian given name of Giorgi Balanchivadze, the birth name of famed choreographer George Balanchine.
-
C.
Jorjadze
Jorjadze is a Georgian noble family name historically associated with aristocracy, landownership, and cultural influence in Georgia.
-
D.
Gurieli
Gurieli was a hereditary princely title held by a noble family that ruled the region of Guria in western Georgia.
-
E.
Giorgi Chanturia
Giorgi Chanturia was a prominent Georgian politician and activist who played a key leadership role in Georgia’s late Soviet-era national independence movement.
- 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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e14ca96c588190922b1f7556dd08cf |
completed | April 16, 2026, 8:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fff28f63c88190968ecbd4706b1331 |
completed | May 10, 2026, 2:50 a.m. |
Created at: April 10, 2026, 4:50 a.m.