Triple
T16978255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egyptian–Nubian relations |
E411870
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient international relations |
C16758
|
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: ancient international relations Context triple: [Egyptian–Nubian relations, instanceOf, ancient international relations]
-
A.
history of the ancient world
The history of the ancient world examines the civilizations, cultures, events, and interactions of human societies from the earliest recorded times to the fall of the Western Roman Empire.
-
B.
diplomatic history
chosen
Diplomatic history is the study of how states and other international actors conduct relations, negotiate agreements, and manage conflicts over time through diplomacy and foreign policy.
-
C.
historical polities
Historical polities are organized political entities or governing structures that existed in the past, such as kingdoms, empires, city-states, and federations, defined by their territorial control, institutions, and sociopolitical systems.
-
D.
international relations
International relations is the study and practice of how states and other global actors interact, cooperate, and conflict within the international system.
-
E.
ancient Anatolian polities
Ancient Anatolian polities were the diverse city-states, kingdoms, and empires that arose in the region of Anatolia (modern-day Turkey), including powers such as the Hittites, Lydians, Phrygians, and others, which played key roles in the political and cultural dynamics of the ancient Near East and Mediterranean.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:32 a.m.