Triple

T17287702
Position Surface form Disambiguated ID Type / Status
Subject Mediterranean Region E419701 entity
Predicate contains P35 FINISHED
Object Burdur 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: Burdur | Statement: [Mediterranean Region, contains, Burdur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Burdur
Context triple: [Mediterranean Region, contains, Burdur]
  • A. Burdur chosen
    Burdur is a city in southwestern Turkey known for its nearby lakes, archaeological sites, and traditional Ottoman-era architecture.
  • B. Milas
    Milas is a town in southwestern Turkey known for its rich ancient Carian and Roman heritage and numerous archaeological sites.
  • C. Kütahya
    Kütahya is a historic city in western Turkey known for its Ottoman-era architecture and traditional ceramic and tile production.
  • D. Nevşehir
    Nevşehir is a city in central Turkey that serves as the main urban center and gateway to the historic, cave-dotted region of Cappadocia.
  • E. Afyon
    Afyon is the former name of Afyonkarahisar, a city in western Turkey known for its strategic location, thermal springs, and opium poppy production.
  • 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_69d886db32608190a61e18862c5a8af6 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e43780fad88190b82193c8335e2f11 completed April 19, 2026, 2:01 a.m.
Created at: April 10, 2026, 5:40 a.m.