Triple
T9498396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noe Ramishvili |
E229071
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Ramishvili |
E229071
|
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: Ramishvili | Statement: [Noe Ramishvili, familyName, Ramishvili]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ramishvili Context triple: [Noe Ramishvili, familyName, Ramishvili]
-
A.
Arsukidze
Arsukidze was a medieval Georgian architect renowned as the master builder of the Svetitskhoveli Cathedral in Mtskheta.
-
B.
Jorjadze
Jorjadze is a Georgian noble family name historically associated with aristocracy, landownership, and cultural influence in Georgia.
-
C.
Javakhishvili
Javakhishvili is a Georgian surname most notably associated with prominent figures such as writer Mikheil Javakhishvili.
-
D.
Noe Ramishvili
chosen
Noe Ramishvili was a Georgian socialist politician and statesman who played a leading role in Georgia’s brief independence after World War I.
-
E.
Robakidze
Robakidze is a Georgian surname most notably borne by the writer and public figure Grigol Robakidze.
- 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_69ca84753660819098e8d416e89e26ae |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd95ef06b88190b7a840caddea3e38 |
completed | April 1, 2026, 10:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d12d3aafb88190ac53289039bca88a |
completed | April 4, 2026, 3:24 p.m. |
Created at: March 30, 2026, 7:56 p.m.