Triple

T13340509
Position Surface form Disambiguated ID Type / Status
Subject Richard III’s royal army E317811 entity
Predicate instanceOf P0 FINISHED
Object armed forces of the Kingdom of England C14911 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 Kingdom of England
Context triple: [Richard III’s royal army, instanceOf, armed forces of the Kingdom of England]
  • A. Parliamentarian army
    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. 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.
  • C. royal army chosen
    A royal army is a formally organized, state-sanctioned military force that serves, protects, and enforces the authority and interests of a monarchy.
  • D. Royal Navy and Army contingent
    A Royal Navy and Army contingent is a combined military unit composed of personnel from both the Royal Navy and the British Army, organized for joint operations, ceremonial duties, or specific missions.
  • E. British military personnel of the Napoleonic Wars
    Individuals who served in the armed forces of the United Kingdom during the Napoleonic Wars (circa 1803–1815), including soldiers, sailors, and officers involved in military operations against Napoleonic France and its allies.
  • 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_69d806b5a3c08190b42c267fb092f98a completed April 9, 2026, 8:06 p.m.
Created at: April 9, 2026, 9:31 p.m.