Triple
T15181897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Persian satraps |
E362766
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Achaemenid administrative office |
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 administrative office Context triple: [Persian satraps, instanceOf, Achaemenid administrative office]
-
A.
Achaemenid institution
chosen
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.
-
B.
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.
-
C.
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.
-
D.
Achaemenid art collection
A curated assemblage of artworks, artifacts, and decorative objects produced under the Achaemenid Empire, reflecting its imperial ideology, cross-cultural influences, and distinctive aesthetic styles.
-
E.
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.
- 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_69d85a09a39c81908759f23268e2d408 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:09 a.m.