Triple

T16444855
Position Surface form Disambiguated ID Type / Status
Subject Mazaca E399397 entity
Predicate hasModernSuccessor P32013 FINISHED
Object Kayseri E152975 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: Kayseri | Statement: [Mazaca, hasModernSuccessor, Kayseri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kayseri
Context triple: [Mazaca, hasModernSuccessor, Kayseri]
  • A. Kayseri chosen
    Kayseri is a historic city in central Turkey, known for its Seljuk and Ottoman architectural heritage and its role as a major commercial and cultural center in Anatolia.
  • B. Konya
    Konya is a major city in central Anatolia known for its rich Seljuk heritage and as the home of the Sufi mystic Rumi and the Whirling Dervishes.
  • C. Samsun
    Samsun is a major Turkish port city on the Black Sea coast, known as an important regional hub for maritime trade and industry.
  • D. Eskişehir
    Eskişehir is a major university and industrial city in northwestern Turkey, known for its vibrant student life, modern urban design, and rich cultural heritage.
  • E. Karacabey
    Karacabey is a town and district in northwestern Turkey known for its agriculture and proximity to both the Marmara Sea and the city of Bursa.
  • 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_69d87f2c6778819080fcfae53be8f12a completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e32cdb5d908190bb6c5cb3c794cf4b completed April 18, 2026, 7:03 a.m.
NED1 Entity disambiguation (via context triple) batch_6a012ec5c99c819082f154267c246e92 completed May 11, 2026, 1:20 a.m.
Created at: April 10, 2026, 5:10 a.m.