Triple
T30551247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amun division |
E777564
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | New Kingdom Egyptian army formation |
C19405
|
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: New Kingdom Egyptian army formation Context triple: [Amun division, instanceOf, New Kingdom Egyptian army formation]
-
A.
army formation
chosen
An army formation is an organized arrangement of military units and personnel on the battlefield or during maneuvers, designed to optimize command, movement, and combat effectiveness.
-
B.
Egyptian military expedition
An Egyptian military expedition is a state-organized campaign in which Egyptian armed forces are deployed beyond their usual boundaries to achieve strategic, political, or economic objectives through armed force and related operations.
-
C.
Renaissance military tradition
Renaissance military tradition encompasses the evolving practices, technologies, doctrines, and social institutions of warfare in Europe between the 14th and 17th centuries, marked by the transition from feudal levies to professional armies, the rise of gunpowder weapons, and the integration of humanist thought into military theory.
-
D.
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.
-
E.
legendary army
A legendary army is a renowned military force whose extraordinary prowess, historic victories, and enduring reputation elevate it to near-mythic status in collective memory.
- 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_69f2249e19108190a458ab446096bf22 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:20 p.m.