Triple
T37962721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karto-Zan branch |
E947048
|
entity |
| Predicate | hasClosestRelativeOf |
P196167
|
FINISHED |
| Object | Georgian language |
E40852
|
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: Georgian language | Statement: [Karto-Zan branch, hasClosestRelativeOf, Georgian language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClosestRelativeOf Context triple: [Karto-Zan branch, hasClosestRelativeOf, Georgian language]
-
A.
hasCloseRelative
Indicates that one entity has another entity as a close family member, such as a parent, child, sibling, or similarly near relative.
-
B.
hasRelativeLocation
Indicates that one entity is positioned in space in relation to another entity’s location.
-
C.
hasRelativeRole
Indicates that one entity holds a familial or kinship-based role in relation to another entity.
-
D.
isRelativeTo
Indicates that one entity has a familial or kinship relationship to another entity.
-
E.
hasRelativeInCast
Indicates that an individual has a family member who is part of the cast of a given production.
- F. None of above. chosen
Provenance (5 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_69f76ef7062c819091bfacb7e83aa1e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe0d165a48819098b854318a50d76c |
completed | May 8, 2026, 4:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a412caa5e848190a2db41496dbeed42 |
completed | June 28, 2026, 2:16 p.m. |
| PD | Predicate disambiguation | batch_69fe0931002481908a95b34f95e9f64e |
completed | May 8, 2026, 4:02 p.m. |
| PDg | Predicate description generation | batch_69fe0d14778c8190986fa4f37f992a2f |
completed | May 8, 2026, 4:19 p.m. |
Created at: May 3, 2026, 4:20 p.m.