Triple
T3011707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | მტკვარი |
E82235
|
entity |
| Predicate | გამდინარე_ქალაქი |
P44977
|
FINISHED |
| Object | თბილისი ისტორიულად ჩამოყალიბდა მტკვრის ნაპირზე |
—
|
LITERAL 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: თბილისი ისტორიულად ჩამოყალიბდა მტკვრის ნაპირზე | Statement: [მტკვარი, გამდინარე_ქალაქი, თბილისი ისტორიულად ჩამოყალიბდა მტკვრის ნაპირზე]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: გამდინარე_ქალაქი Context triple: [მტკვარი, გამდინარე_ქალაქი, თბილისი ისტორიულად ჩამოყალიბდა მტკვრის ნაპირზე]
-
A.
city2
Indicates a relationship where one entity is identified as a city associated with, located in, or otherwise linked to another entity.
-
B.
cityName
Indicates that the associated value is the name of a city.
-
C.
city1
Indicates that the subject is classified as a city.
-
D.
metropolitanOf
Indicates that one place serves as the primary metropolitan center or core urban area for another place or region.
-
E.
ancientCity
Indicates that the subject is a historically old or long-established city, typically originating from ancient times.
- F. None of above. chosen
Provenance (4 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_69ad8b1eb53481908c39bbcd1ec104b2 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a66c334819082d1d320c48eca1b |
completed | March 8, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69ad961a97188190809dc73430a8eda8 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97ba55dc8190b6dddddfb751cf64 |
completed | March 8, 2026, 3:37 p.m. |
Created at: March 8, 2026, 3 p.m.