Triple

T20649394
Position Surface form Disambiguated ID Type / Status
Subject Beylik of Eretna E507446 entity
Predicate capital P234 FINISHED
Object Kayseri NE NERFINISHED

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: [Beylik of Eretna, capital, Kayseri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kayseri
Context triple: [Beylik of Eretna, capital, 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 (2 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_69e0b4bf58c081908e52a4500e03ff83 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6af2076b48190b9c8afb4eac65f46 completed April 20, 2026, 10:56 p.m.
Created at: April 16, 2026, 11:43 a.m.