Triple
T37859200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parliamentarian forces in Ireland |
E944275
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | armed forces of the English Parliament |
C29732
|
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: armed forces of the English Parliament Context triple: [Parliamentarian forces in Ireland, instanceOf, armed forces of the English Parliament]
-
A.
Parliamentarian army
chosen
A Parliamentarian army is a military force organized, funded, and directed by a parliamentary body to wage war or maintain order in support of its political authority and policies.
-
B.
Angevin army
The Angevin army was the military force of the Angevin kings of England and their continental domains, composed of feudal levies, mercenaries, and household troops used to defend and expand their vast 12th–13th century empire.
-
C.
formation of the British Armed Forces
The formation of the British Armed Forces refers to the historical process by which England’s separate military services—Army, Royal Navy, and later Royal Air Force—evolved, professionalized, and were unified under the authority of the British state to create a coordinated national defense establishment.
-
D.
British imperial forces
British imperial forces: the military, naval, and auxiliary units raised, organized, or commanded by the British Empire to project power, maintain control, and defend its interests across its colonies and territories.
-
E.
royal army
A royal army is a formally organized, state-sanctioned military force that serves, protects, and enforces the authority and interests of a monarchy.
- 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_69f76eee2f9c8190b1272aa2ee55ebf5 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.