Triple
T11882409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Persian court |
E282690
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Achaemenid institution |
C30543
|
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: Achaemenid institution Context triple: [Persian court, instanceOf, Achaemenid institution]
-
A.
Achaemenid architecture
Achaemenid architecture is the monumental building style of the first Persian Empire, characterized by grand palatial complexes, tall stone columns, elaborate reliefs, and a synthesis of Mesopotamian, Egyptian, and Anatolian influences.
-
B.
Achaemenid province
An Achaemenid province is an administrative region within the Achaemenid Persian Empire, governed by a satrap or local authority responsible for taxation, security, and implementing imperial policies.
-
C.
ancient Iranian dynasty
An ancient Iranian dynasty is a long-ruling hereditary line of monarchs originating in the Iranian cultural sphere that governed significant territories in antiquity, shaping the region’s political, social, and religious history.
-
D.
Achaemenid noble
An Achaemenid noble is a high-ranking member of the Persian aristocracy who held land, military command, and administrative authority under the Achaemenid Empire, often serving as a close supporter and regional representative of the Great King.
-
E.
Achaemenid inscription
An Achaemenid inscription is a formal text carved or written on durable materials during the Achaemenid Empire, typically in multiple languages and scripts, to record royal proclamations, commemorations, or religious dedications.
- F. None of above. chosen
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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:44 p.m.