Triple
T315949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kutaisi |
E7705
|
entity |
| Predicate | wasCapitalDuring |
P3417
|
FINISHED |
| Object | United Kingdom of Georgia period |
—
|
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: United Kingdom of Georgia period | Statement: [Kutaisi, wasCapitalDuring, United Kingdom of Georgia period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasCapitalDuring Context triple: [Kutaisi, wasCapitalDuring, United Kingdom of Georgia period]
-
A.
wasFirstCapitalOf
Indicates that one place previously served as the earliest or original capital city of another political or administrative entity.
-
B.
formerCapitalOf
chosen
Indicates that a place once served as the capital of another entity (such as a country or region) but no longer holds that status.
-
C.
servedAsUSCapitalFrom
Indicates that a location functioned as the capital of the United States during a specified time period.
-
D.
servedAsUSCapitalUntil
Indicates that a place functioned as the capital of the United States up to a specified end date.
-
E.
inauguratedAsCapital
Indicates that a place was officially declared and established as the capital of a political or administrative 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea6462148190825acc57f6d2adaf |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e943f12c8190883854aeed974260 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.