Triple
T9044809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osiauri |
E216726
|
entity |
| Predicate | hasRegionalCapital |
P3877
|
FINISHED |
| Object | Gori |
E1743
|
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: Gori | Statement: [Osiauri, hasRegionalCapital, Gori]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gori Context triple: [Osiauri, hasRegionalCapital, Gori]
-
A.
Gori
chosen
Gori is a city in central Georgia best known as the birthplace of Soviet leader Joseph Stalin.
-
B.
Goris
Goris is a town in southern Armenia known for its historic stone houses, surrounding cave dwellings, and role as a regional cultural and transportation hub.
-
C.
Didgori
Didgori is a historic site in eastern Georgia renowned as the location of the decisive 1121 battle where King David IV’s forces defeated the Seljuk Turks.
-
D.
Gorie
Gorie is a small settlement located near Cullingsburgh in the Shetland Islands of Scotland.
-
E.
Gorgany
Gorgany is a rugged mountain range in the Eastern Carpathians of western Ukraine, known for its dense forests, rocky terrain, and rich biodiversity.
- 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_69ca83d22d488190adbce5e020e9cd1d |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6b137cec8190bd1b812c10d9542a |
completed | April 1, 2026, 12:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cffdb868e48190b9d193025cb5b9a2 |
completed | April 3, 2026, 5:49 p.m. |
Created at: March 30, 2026, 7:09 p.m.