Triple
T23848143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conquest of Sudan |
E592080
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Egyptian conquest |
C43862
|
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: Egyptian conquest Context triple: [Conquest of Sudan, instanceOf, Egyptian conquest]
-
A.
Egyptian military expedition
chosen
An Egyptian military expedition is a state-organized campaign in which Egyptian armed forces are deployed beyond their usual boundaries to achieve strategic, political, or economic objectives through armed force and related operations.
-
B.
Assyrian conquest
Assyrian conquest refers to the aggressive military expansion and subjugation of neighboring regions by the ancient Assyrian Empire, characterized by advanced warfare tactics, strategic deportations, and administrative control to build a powerful Near Eastern empire.
-
C.
Mongol conquest
The Mongol conquest refers to the series of 13th- and 14th-century military campaigns by the Mongol Empire that rapidly expanded its rule across Eurasia through highly mobile warfare, psychological tactics, and administrative integration of conquered peoples.
-
D.
Theban
Theban is a conceptual class representing anything related to the ancient Egyptian city of Thebes, including its people, culture, artifacts, and historical context.
-
E.
Mongol invasion of the Middle East
The Mongol invasion of the Middle East was a series of 13th- and 14th-century military campaigns by the Mongol Empire that devastated major Islamic centers, reshaped regional political structures, and facilitated new patterns of trade and cultural exchange across Eurasia.
- 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_69e25d221d908190b9b502ad31e66a3f |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 8:10 p.m.