Triple
T7681273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Kars |
E173998
|
entity |
| Predicate | hasLocation |
P40
|
FINISHED |
| Object | Kars |
E199207
|
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: Kars | Statement: [Siege of Kars, hasLocation, Kars]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kars Context triple: [Siege of Kars, hasLocation, Kars]
-
A.
Kars
chosen
Kars is a historic city in northeastern Turkey known for its medieval fortifications, strategic location near the Caucasus, and role as a former regional capital in various Armenian and Ottoman periods.
-
B.
Karad
Karad is a town in the Satara district of Maharashtra, India, known for its location at the confluence of the Krishna and Koyna rivers and its regional commercial and educational significance.
-
C.
Kirovakan
Kirovakan is the former name of Vanadzor, a major industrial city in northern Armenia.
-
D.
Karatay
Karatay is a central district and municipality within Turkey’s Konya Province, known for its historical sites and role in the urban core of Konya city.
-
E.
Karak
Karak is a town in Pakistan’s Khyber Pakhtunkhwa province known as the headquarters of Karak District and for its surrounding oil and gas reserves.
- 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_69c6995840408190a19de6c51090f46f |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c701ffc1fc8190bc9c2b1f3bb37f0d |
completed | March 27, 2026, 10:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8a24de3a48190a92009b6092b09d0 |
completed | March 29, 2026, 3:53 a.m. |
Created at: March 27, 2026, 4:01 p.m.