Triple
T5904656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ottoman Syria |
E131314
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former Ottoman territory |
C10122
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: former Ottoman territory Context triple: [Ottoman Syria, instanceOf, former Ottoman territory]
-
A.
part of the Ottoman Empire
chosen
A "part of the Ottoman Empire" is a territorial, administrative, or political subdivision that was under the sovereignty and governance of the Ottoman state during its existence.
-
B.
Turkish principality
A Turkish principality is a semi-independent, territorially defined political entity ruled by a Turkish dynastic leader, typically emerging in the medieval or early modern period within the broader context of Turkic state formation and regional power dynamics.
-
C.
former sovereign state
A former sovereign state is a political entity that once possessed full independence and international recognition as a nation but has since lost that status through dissolution, merger, annexation, or other political change.
-
D.
former constituent country
A former constituent country is a previously existing political entity that once formed part of a larger sovereign state or union but has since been dissolved, restructured, or gained a different political status.
-
E.
former Italian colony
A former Italian colony is a territory that was once under the political control and administration of the Kingdom of Italy or Italian state but has since gained independence or been transferred to another sovereign power.
- F. None of above.
Provenance (1 batch)
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_69c0085864a88190a569c05ff7d65f29 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:59 p.m.