Triple
T18445277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artuqid forces |
E450638
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval military force |
C40700
|
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: medieval military force Context triple: [Artuqid forces, instanceOf, medieval military force]
-
A.
medieval military leader
A medieval military leader is a high-ranking commander responsible for organizing, directing, and inspiring armed forces in warfare during the Middle Ages, often balancing battlefield tactics with feudal, political, and religious obligations.
-
B.
medieval Christian warriors
Medieval Christian warriors were armed combatants, such as knights and crusaders, who fought under the banner of Christian faith and feudal allegiance in religiously and politically motivated conflicts.
-
C.
Parliamentarian cavalry
Parliamentarian cavalry were mounted troops loyal to the English Parliament during the Civil War, combining mobility, shock tactics, and disciplined formations to challenge Royalist forces on the battlefield.
-
D.
peasant army
A peasant army is a loosely organized military force composed primarily of rural commoners, often mobilized in response to oppression, invasion, or social upheaval rather than as a standing professional army.
-
E.
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.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:30 a.m.