Triple
T35068311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beating Retreat |
E1011796
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British military tradition |
C32126
|
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 military tradition Context triple: [Beating Retreat, instanceOf, British military tradition]
-
A.
Royal Navy tradition
Royal Navy tradition encompasses the long-established customs, ceremonies, values, and practices that shape the identity, discipline, and heritage of the United Kingdom’s naval service.
-
B.
British Army custom
chosen
A British Army custom is a traditional, informally codified practice or ritual observed by soldiers that reflects the Army’s history, values, and regimental identity.
-
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 Army order
A British Army order is an official directive issued by a competent military authority within the British Army that prescribes specific actions, procedures, or policies to be followed by subordinate personnel.
-
E.
U.S. Army tradition
U.S. Army tradition encompasses the long-standing customs, values, ceremonies, and shared history that shape the identity, discipline, and esprit de corps of the United States Army.
- 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_69f76dd193108190af2528186f25b72a |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.