Triple

T19035184
Position Surface form Disambiguated ID Type / Status
Subject Burdur E465847 entity
Predicate nearbyCity P350 FINISHED
Object Isparta 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: Isparta | Statement: [Burdur, nearbyCity, Isparta]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Isparta
Context triple: [Burdur, nearbyCity, Isparta]
  • A. Isparta chosen
    Isparta is a city in southwestern Turkey known for its rose cultivation and production of rose oil and related products.
  • B. Manisa
    Manisa is a historic city in western Turkey known for its agricultural production, especially grapes and olives, and its proximity to the Aegean coast.
  • C. Isparta Province
    Isparta Province is an inland region of southwestern Turkey known for its rose cultivation, lakes, and agricultural production.
  • D. Viranşehir
    Viranşehir is a town and district in southeastern Turkey known for its agricultural economy and location within Şanlıurfa Province near the Syrian border.
  • E. Gedera
    Gedera is a town in central Israel known for its agricultural roots and diverse immigrant communities.
  • 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_69d8dd0359648190bc2a9202c5cf29d2 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d7438f748190912c28912e6b97a6 completed April 20, 2026, 7:35 a.m.
Created at: April 10, 2026, 12:02 p.m.