Triple
T2274830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Almaty |
E50745
|
entity |
| Predicate | formerName |
P65
|
FINISHED |
| Object | Alma-Ata |
E50745
|
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: Alma-Ata | Statement: [Almaty, formerName, Alma-Ata]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Alma-Ata Context triple: [Almaty, formerName, Alma-Ata]
-
A.
Alma-Atinskaya
Alma-Atinskaya is a southern terminus station of the Moscow Metro, serving as one endpoint of the Zamoskvoretskaya Line.
-
B.
Karaganda
Karaganda is a large industrial city in central Kazakhstan known for its coal mining industry and Soviet-era history.
-
C.
Almaty
chosen
Almaty is the largest city and main commercial and cultural center of Kazakhstan, located in the country’s mountainous southeast.
-
D.
Kaspiysk
Kaspiysk is a coastal city on the Caspian Sea in the Republic of Dagestan, Russia, known for its industrial base and strategic naval facilities.
-
E.
Karshi
Karshi is a city in southern Uzbekistan known as an important regional center for industry, agriculture, and transportation.
- 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_69a88b05910c8190a9a2b1ff230c85f9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc1ebaa148190851952567878b3a1 |
completed | March 7, 2026, 6:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69aef08a105081908455f482c6b2a880 |
completed | March 9, 2026, 4:08 p.m. |
Created at: March 4, 2026, 7:48 p.m.