Triple
T15777412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baku City Executive Power |
E382524
|
entity |
| Predicate | jurisdiction |
P82
|
FINISHED |
| Object | City of Baku |
E81696
|
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: City of Baku | Statement: [Baku City Executive Power, jurisdiction, City of Baku]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: City of Baku Context triple: [Baku City Executive Power, jurisdiction, City of Baku]
-
A.
Baku
chosen
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.
-
B.
Shamakhi
Shamakhi is a historic city in Azerbaijan known for its long-standing Jewish community and cultural significance in the region.
-
C.
Kizlyar
Kizlyar is a town in the Republic of Dagestan, Russia, known historically as a frontier settlement and trading center in the North Caucasus region.
-
D.
Bulaq
Bulaq is a historic district of Cairo, Egypt, known for its past role as a major port and commercial hub along the Nile.
-
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_69d86da09a10819082fe9797b23e4664 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e05199cd8881909462462cec34d35a |
completed | April 16, 2026, 3:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffb59779788190a393237f5293fe8d |
completed | May 9, 2026, 10:30 p.m. |
Created at: April 10, 2026, 4:47 a.m.