Triple
T546117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neo-Babylonian Empire |
E12736
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mesopotamian polity |
C984
|
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: Mesopotamian polity Context triple: [Neo-Babylonian Empire, instanceOf, Mesopotamian polity]
-
A.
ancient civilization
chosen
An ancient civilization is a complex, organized society from antiquity characterized by urban development, social stratification, specialized labor, centralized governance, and enduring cultural, technological, and architectural achievements.
-
B.
Islamic empire
An Islamic empire is a large, multi-ethnic political entity historically governed by Muslim rulers who derive authority from Islamic law and tradition, integrating religious, cultural, and administrative systems across vast territories.
-
C.
early modern polity
An early modern polity is a territorially bounded, politically organized community between roughly 1500 and 1800 that exercised authority through evolving institutions of governance, law, and sovereignty amid processes of state formation and imperial expansion.
-
D.
early modern state
An early modern state is a centralized political entity that emerged in Europe between the 15th and 18th centuries, characterized by growing bureaucratic administration, territorial sovereignty, standing armies, and increasingly standardized systems of law and taxation.
-
E.
dynasty
A dynasty is a succession of rulers or leaders from the same family or lineage, often maintaining power over multiple generations within a state or organization.
- 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_69a49334226c81908b0ea1689ef6aa3f |
completed | March 1, 2026, 7:27 p.m. |
Created at: March 1, 2026, 7:32 p.m.