Triple
T17097709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batum district |
E414891
|
entity |
| Predicate | centeredOn |
P164
|
FINISHED |
| Object | Batum |
E41677
|
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: Batum | Statement: [Batum district, centeredOn, Batum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Batum Context triple: [Batum district, centeredOn, Batum]
-
A.
Batumi
chosen
Batumi is a major Black Sea resort city in southwestern Georgia known for its beaches, modern skyline, and role as a regional economic and cultural hub.
-
B.
Baku
Baku is the capital and largest city of Azerbaijan, known for its rich blend of Islamic heritage and modern architecture on the shores of the Caspian Sea.
-
C.
Sheki
Sheki is a historic city in northwestern Azerbaijan, renowned for its preserved Silk Road-era architecture, caravanserais, and rich culinary traditions.
-
D.
Batum district
Batum district was a historical administrative region centered on the Black Sea port city of Batum (now Batumi), strategically important in the Caucasus and contested between the Ottoman and Russian Empires.
-
E.
Bulaq
Bulaq were a Turkic tribal group historically associated with the Karluk confederation in Central Asia.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbfe92988190aa066745ca9791d5 |
completed | April 18, 2026, 7:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a012eefd5f08190b9eb8a81e45a9921 |
completed | May 11, 2026, 1:20 a.m. |
Created at: April 10, 2026, 5:35 a.m.