Triple
T18390697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Jaysh al-ʿArabī |
E449717
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial-era military force |
C40449
|
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: colonial-era military force Context triple: [al-Jaysh al-ʿArabī, instanceOf, colonial-era military force]
-
A.
private colonial army
A private colonial army is a non-state military force organized and funded by a colonial power or its chartered companies to secure territory, enforce control, and protect economic interests in colonized regions.
-
B.
British colonial regiment
A British colonial regiment is a military unit raised, organized, and commanded by the British Empire from its overseas colonies, typically composed of local recruits led by British officers to serve imperial defense and expansion.
-
C.
Spanish imperial military unit
A Spanish imperial military unit is an organized armed formation under the authority of the Spanish Empire, structured for conquest, defense, and control of its territories across Europe and overseas.
-
D.
Dutch colonial military campaign
A Dutch colonial military campaign is an organized series of armed operations conducted by the Netherlands to conquer, pacify, or control territories and populations within its overseas empire.
-
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_69d8b9fab8a8819086a9ddc0871715e0 |
completed | April 10, 2026, 8:51 a.m. |
Created at: April 10, 2026, 10:46 a.m.