Triple
T7303230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ottoman Empire |
E167910
|
entity |
| Predicate | capital |
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 Empire, capital, Edirne]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Edirne Context triple: [Ottoman Empire, capital, 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.
Edirne Vilayet
Edirne Vilayet was an administrative province of the late Ottoman Empire centered on the city of Edirne in the European (Rumelian) part of the empire.
-
C.
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.
-
D.
Targovishte
Targovishte is a town in northeastern Bulgaria known as an administrative and economic center with historical roots dating back to the Ottoman period.
-
E.
Ardahan
Ardahan is a town in northeastern Turkey that serves as the capital of Ardahan Province near the border with Georgia.
- 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_69c6888c820881909fc68f689fe1c251 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ebb2261c8190ae9095c8e110b528 |
completed | March 27, 2026, 8:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7e558098c819091562566c59332e2 |
completed | March 28, 2026, 2:27 p.m. |
Created at: March 27, 2026, 3:01 p.m.