Triple
T8624530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nana Djordjadze |
E204250
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Djordjadze |
E713408
|
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: Djordjadze | Statement: [Nana Djordjadze, familyName, Djordjadze]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Djordjadze Context triple: [Nana Djordjadze, familyName, Djordjadze]
-
A.
Jorjadze
chosen
Jorjadze is a Georgian noble family name historically associated with aristocracy, landownership, and cultural influence in Georgia.
-
B.
Ilija
Ilija is a masculine given name of Slavic origin, commonly used in countries such as Bulgaria, Serbia, and North Macedonia.
-
C.
Arapov
Arapov is a Slavic masculine surname commonly found in Russian-speaking countries.
-
D.
Robakidze
Robakidze is a Georgian surname most notably borne by the writer and public figure Grigol Robakidze.
-
E.
Dimitar
Dimitar is a masculine given name of Slavic origin, commonly used in Bulgaria and other Eastern European countries.
- 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_69ca834a4ea0819094970dceb9e389f3 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4728360c8190b5e600596cbced0c |
completed | March 31, 2026, 10:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cebbe6a7e48190a166a31dccd8ac16 |
completed | April 2, 2026, 6:56 p.m. |
Created at: March 30, 2026, 6:26 p.m.