Triple

T5491978
Position Surface form Disambiguated ID Type / Status
Subject Asian Turkey E123721 entity
Predicate containsCity P294 FINISHED
Object Edirne E19465 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: Edirne | Statement: [Asian Turkey, containsCity, Edirne]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Edirne
Context triple: [Asian Turkey, containsCity, Edirne]
  • A. Edirne chosen
    Edirne is a historic city in northwestern Turkey that served as an early capital of the Ottoman Empire and is renowned for its Ottoman-era architecture, including the Selimiye Mosque.
  • B. Kırklareli
    Kırklareli is a city in northwestern Turkey known for its location near the Bulgarian border, agricultural economy, and historical Ottoman-era architecture.
  • C. Ardahan
    Ardahan is a town in northeastern Turkey that serves as the capital of Ardahan Province near the border with Georgia.
  • D. Vidin
    Vidin is a historic city and river port in northwestern Bulgaria on the Danube, known for its medieval fortress and role as a regional center during the Second Bulgarian Empire.
  • E. Silistra
    Silistra is a historic city in northeastern Bulgaria on the Danube River, known as an important cultural and economic center of the Dobruja region.
  • 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_69bd464a2d908190869324ce176779c8 completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd9280403c8190baaa3f7923449a37 completed March 20, 2026, 6:31 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf70dcb0c881909d9aaf0050a5c27b completed March 22, 2026, 4:32 a.m.
Created at: March 20, 2026, 2:10 p.m.