Triple
T33687894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Army Ceremonial Units |
E863091
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military ceremonial formation |
C31861
|
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: military ceremonial formation Context triple: [United States Army Ceremonial Units, instanceOf, military ceremonial formation]
-
A.
army formation
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.
military formation tradition
chosen
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.
-
C.
military formation concept
A military formation concept is an abstract representation of how armed forces are organized, arranged, and maneuvered on the battlefield to achieve tactical or strategic objectives.
-
D.
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.
-
E.
militia-style military formation
A militia-style military formation is an organized group of primarily non-professional, part-time fighters drawn from the civilian population, structured for local defense or irregular warfare under limited formal military hierarchy and training.
- 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_69f3498662b48190904442c39df84fb7 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:43 a.m.