Triple
T16387983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maria Svanidze |
E397972
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Svanidze |
E1201188
|
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: Svanidze | Statement: [Maria Svanidze, familyName, Svanidze]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Svanidze Context triple: [Maria Svanidze, familyName, Svanidze]
-
A.
Svanidze
chosen
Svanidze is a Georgian surname most notably associated with the family of Joseph Stalin’s first wife, Kato Svanidze.
-
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.
Leselidze
Leselidze is a Georgian surname most notably associated with Soviet military commander Konstantin Leselidze.
-
E.
Gurieli
Gurieli was a hereditary princely title held by a noble family that ruled the region of Guria in western 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e3263f18988190800b921381d60c1b |
completed | April 18, 2026, 6:35 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00356ed47c819085aaf101459dd55c |
completed | May 10, 2026, 7:36 a.m. |
Created at: April 10, 2026, 5:08 a.m.