Triple
T18445399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sökmen of Mardin |
E450641
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Turkoman military leader |
C40179
|
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: Turkoman military leader Context triple: [Sökmen of Mardin, instanceOf, Turkoman military leader]
-
A.
Turkic military leader
chosen
A Turkic military leader is a commander of Turkic origin who organizes, directs, and leads armed forces in warfare, defense, or expansion, often shaping the political and cultural trajectory of Turkic societies.
-
B.
Persian military commander
A Persian military commander is a high-ranking leader responsible for planning, directing, and overseeing the armed forces of Persia in warfare and defense operations.
-
C.
Turkish military officer
A Turkish military officer is a commissioned member of Türkiye’s armed forces responsible for leading personnel, planning and executing military operations, and upholding national security and constitutional order.
-
D.
Ottoman general
An Ottoman general is a high-ranking military commander in the Ottoman Empire responsible for planning, leading, and overseeing major military campaigns and the administration of troops.
-
E.
Assyrian general
An Assyrian general is a high-ranking military commander in the ancient Assyrian Empire responsible for planning campaigns, leading armies in battle, and enforcing the king’s authority through warfare and conquest.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:30 a.m.