Triple
T4128185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Army under Cornwallis |
E92774
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British field army |
C1740
|
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: British field army Context triple: [British Army under Cornwallis, instanceOf, British field army]
-
A.
British Army organizational element
chosen
A British Army organizational element is a defined structural unit—such as a section, platoon, company, battalion, brigade, or division—comprising personnel, equipment, and command relationships arranged to perform specific military roles within the Army’s hierarchy.
-
B.
British Army deployment
British Army deployment is the organized assignment and movement of British Army personnel and resources to specific locations or operations to fulfill military objectives and commitments.
-
C.
British Army position
A British Army position is a specific role or rank within the British Army’s organizational structure, defining an individual’s responsibilities, authority, and place in the military hierarchy.
-
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.
German field army
A German field army is a large, operational-level military formation of the German armed forces, typically composed of multiple corps and supporting units, organized to conduct sustained land campaigns in a defined theater of war.
- 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_69aed9685f70819086932777aec8d959 |
completed | March 9, 2026, 2:30 p.m. |
Created at: March 9, 2026, 3:42 p.m.