Triple
T30376222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bagration |
E772695
|
entity |
| Predicate | hasFamilyNameInGeorgian |
P27865
|
FINISHED |
| Object | ბაგრატიონი |
—
|
NE NERFINISHED |
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: ბაგრატიონი | Statement: [Bagration, hasFamilyNameInGeorgian, ბაგრატიონი]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyNameInGeorgian Context triple: [Bagration, hasFamilyNameInGeorgian, ბაგრატიონი]
-
A.
hasFamilyNameInLanguage
chosen
Indicates that an entity has a specific family name as expressed or written in a particular language.
-
B.
hasFamilyNameOf
Indicates that one entity bears or uses the same family name (surname) as another entity.
-
C.
GeorgianName
Indicates that an entity has a name that is in the Georgian language or follows Georgian naming conventions.
-
D.
hasNameInFamily
Indicates that an entity is known or referred to by a particular name within the context of a specific family or familial group.
-
E.
isPatronymicOrFamilyBased
Indicates that one entity’s name is derived from or based on the personal or family name of another entity.
- F. None of above.
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_69f2248e3444819081b05712dc6873de |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: April 29, 2026, 8 p.m.