Triple
T16744160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 23 Parachute Engineer Regiment |
E406905
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | airborne engineer regiment |
C37859
|
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 engineer regiment Context triple: [23 Parachute Engineer Regiment, instanceOf, airborne engineer regiment]
-
A.
airborne corps
An airborne corps is a large military formation composed primarily of paratrooper and air-transportable units, organized and equipped to conduct large-scale airborne operations behind or across enemy lines.
-
B.
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.
-
C.
army aviation corps
The army aviation corps is a military branch responsible for providing aerial support, reconnaissance, transport, and combat capabilities to ground forces using helicopters and other aircraft.
-
D.
air engineering squadron
An air engineering squadron is a military unit responsible for the maintenance, repair, testing, and technical support of aircraft and related aerospace systems to ensure their operational readiness and safety.
-
E.
airborne infantry battalion
An airborne infantry battalion is a highly mobile, lightly equipped military unit trained and organized to deploy rapidly by air and conduct combat operations, often via parachute or air assault, to seize and hold key terrain behind or ahead of front 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:21 a.m.