Triple
T30329256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Urartian royal administration |
E771428
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Near Eastern administrative system |
C51731
|
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 Near Eastern administrative system Context triple: [Urartian royal administration, instanceOf, ancient Near Eastern administrative system]
-
A.
ancient Near Eastern dynasty
An ancient Near Eastern dynasty is a succession of rulers from the same family or lineage that governed a state or empire in the Near East during antiquity, shaping its political, cultural, and religious development over time.
-
B.
ancient Near Eastern law collection
An ancient Near Eastern law collection is a compiled set of legal rules, case decisions, and royal decrees from early civilizations such as Mesopotamia, intended to articulate social norms, regulate behavior, and legitimize authority.
-
C.
Achaemenid institution
An Achaemenid institution is an organized structure or system—political, administrative, religious, economic, or military—established and maintained by the Achaemenid Empire to govern, manage resources, and integrate its diverse territories.
-
D.
royal administration apparatus
chosen
The royal administration apparatus is the organized system of offices, officials, and procedures through which a monarchy governs, manages resources, and enforces its authority over a realm.
-
E.
Syro-Aramean polity
A Syro-Aramean polity is a historical or conceptual political entity rooted in the cultural, linguistic, and territorial interplay of ancient Syrian and Aramean societies in the Near East.
- 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_69f2248aba24819095bb86480d55b23b |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:53 p.m.