Triple

T4869892
Position Surface form Disambiguated ID Type / Status
Subject Ottoman House E109060 entity
Predicate capitalDuringRule P234 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: [Ottoman House, capitalDuringRule, Edirne]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Edirne
Context triple: [Ottoman House, capitalDuringRule, 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. Ardahan
    Ardahan is a town in northeastern Turkey that serves as the capital of Ardahan Province near the border with Georgia.
  • C. 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.
  • D. 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.
  • E. Asenovgrad
    Asenovgrad is a town in southern Bulgaria known as a gateway to the Rhodope Mountains and a regional center rich in historical and religious landmarks.
  • 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_69bd440d96a48190b0c87069adef2af1 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6d9aec60819090f485757038c2a8 completed March 20, 2026, 3:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69be6fb25f008190ab9b7cc904b540c9 completed March 21, 2026, 10:15 a.m.
Created at: March 20, 2026, 1:27 p.m.