Triple
T31100330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Immortals |
E792655
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Achaemenid military formation |
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 military formation Context triple: [Immortals, instanceOf, Achaemenid military formation]
-
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.
ancient Greek military force
An ancient Greek military force is an organized body of citizen-soldiers, often centered around the hoplite phalanx and supported by various specialized units, mobilized by a polis or coalition to conduct warfare and defend its political interests.
-
D.
hoplite army
A hoplite army is a heavily armed infantry force of citizen-soldiers fighting in close formation, typically organized into phalanxes using spears, shields, and armor for collective defense and offense.
-
E.
armored cavalry formation
An armored cavalry formation is a highly mobile, heavily armored military unit organized to conduct reconnaissance, security, and shock action on the battlefield using tanks and other armored fighting vehicles.
- 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_69f224cf157c81909e2d2bd88c9282c3 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:03 p.m.