Triple
T14390491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2nd Battalion Coldstream Guards (Armoured) |
E356826
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | armoured infantry battalion |
C29021
|
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: armoured infantry battalion Context triple: [2nd Battalion Coldstream Guards (Armoured), instanceOf, armoured infantry battalion]
-
A.
mechanized infantry battalion
chosen
A mechanized infantry battalion is a military unit composed of infantry soldiers equipped with armored vehicles that provide protected mobility, firepower, and support for rapid, combined-arms operations on the battlefield.
-
B.
armored infantry division
An armored infantry division is a large, combined-arms military formation that integrates mechanized infantry, tanks, artillery, and support units to conduct sustained offensive and defensive ground operations.
-
C.
anti-tank battalion
An anti-tank battalion is a military unit organized, equipped, and trained specifically to detect, engage, and destroy enemy armored vehicles and tanks using specialized anti-armor weapons and tactics.
-
D.
armored brigade combat team
An armored brigade combat team is a highly mobile, heavily armored combined-arms military formation designed to conduct offensive and defensive ground operations using tanks, mechanized infantry, artillery, and support units.
-
E.
armored regiment
An armored regiment is a military unit equipped primarily with tanks and other armored fighting vehicles, organized to conduct offensive and defensive ground combat operations.
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:16 a.m.