Triple
T13111135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Western Desert Force |
E310972
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British Army field formation |
C19405
|
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 Army field formation Context triple: [British Western Desert Force, instanceOf, British Army field formation]
-
A.
army formation
chosen
An army formation is an organized arrangement of military units and personnel on the battlefield or during maneuvers, designed to optimize command, movement, and combat effectiveness.
-
B.
Royal Marines formation
A Royal Marines formation is an organized, mission-tailored military unit of the Royal Marines, structured and equipped to conduct amphibious, littoral, and expeditionary operations under a unified command.
-
C.
French Army formation
A French Army formation is an organized military unit or grouping within the French Army, structured and equipped to conduct specific operational, tactical, or administrative functions.
-
D.
Continental Army brigade formation
A Continental Army brigade formation was a tactical military unit composed of several regiments organized under a brigadier general, arranged on the battlefield to coordinate infantry, artillery, and support elements during the American Revolutionary War.
-
E.
military formation tradition
A military formation tradition is a customary, often historically rooted practice governing how armed forces arrange, maneuver, and present their units in organized patterns for combat, ceremony, or discipline.
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:05 p.m.