Triple
T9298561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1st Airlanding Anti-Tank Battery, Royal Artillery |
E223701
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | airborne anti-tank unit |
C27163
|
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: airborne anti-tank unit Context triple: [1st Airlanding Anti-Tank Battery, Royal Artillery, instanceOf, airborne anti-tank unit]
-
A.
airborne cavalry unit
An airborne cavalry unit is a highly mobile military force that uses aircraft, typically helicopters, to rapidly deploy troops and conduct reconnaissance, assault, and security operations.
-
B.
army aviation unit
An army aviation unit is a military organization equipped with rotary- and/or fixed-wing aircraft to provide reconnaissance, air assault, transport, close air support, and other aviation capabilities in support of ground forces.
-
C.
armoured corps
An armoured corps is a large military formation composed primarily of tank and mechanized units, designed to deliver rapid, heavily protected offensive and defensive ground operations.
-
D.
airborne infantry division
An airborne infantry division is a large military formation of specially trained soldiers equipped and organized to deploy rapidly by air, typically via parachute or air assault, to seize and hold key objectives behind enemy lines.
-
E.
airborne infantry brigade
An airborne infantry brigade is a highly mobile, light infantry formation trained and equipped to deploy rapidly by air, including parachute or air assault operations, to seize and hold key objectives behind or ahead of enemy lines.
- F. None of above. chosen
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_69ca8423edb08190bc0c91287a484768 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:36 p.m.