Triple

T16377025
Position Surface form Disambiguated ID Type / Status
Subject Sultan Han (Aksaray) E397703 entity
Predicate locatedNear P294 FINISHED
Object Aksaray E351172 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: Aksaray | Statement: [Sultan Han (Aksaray), locatedNear, Aksaray]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aksaray
Context triple: [Sultan Han (Aksaray), locatedNear, Aksaray]
  • A. Aksaray chosen
    Aksaray is a historic city in central Turkey known for its location on the ancient Silk Road and its proximity to the Cappadocia region.
  • B. Amasya
    Amasya is a historic city in northern Turkey, renowned for its Ottoman-era architecture, rock tombs of Pontic kings, and scenic setting along the Yeşilırmak River.
  • C. Afyon
    Afyon is the former name of Afyonkarahisar, a city in western Turkey known for its strategic location, thermal springs, and opium poppy production.
  • D. Kütahya
    Kütahya is a historic city in western Turkey known for its Ottoman-era architecture and traditional ceramic and tile production.
  • E. Çankırı
    Çankırı is a small provincial city in north-central Turkey known for its historical fortifications, salt mines, and location on the Anatolian plateau.
  • 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_69d87f2880b48190ae1a9673a3bbef80 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e319d8a40c8190af37e7ed60b9c4dd completed April 18, 2026, 5:42 a.m.
NED1 Entity disambiguation (via context triple) batch_6a00cfb95b348190a006f699c01e85ce completed May 10, 2026, 6:34 p.m.
Created at: April 10, 2026, 5:08 a.m.