Triple
T18631376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 38th Fighter Group (Republic of Korea Air Force) |
E455424
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | combat aviation unit |
C40810
|
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: combat aviation unit Context triple: [38th Fighter Group (Republic of Korea Air Force), instanceOf, combat aviation unit]
-
A.
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.
-
B.
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.
-
C.
aviation regiment
An aviation regiment is a military unit composed of multiple aircraft squadrons or flights, along with their supporting personnel and equipment, organized to conduct coordinated air operations.
-
D.
army aviation battalion
An army aviation battalion is a military unit that operates and maintains rotary- and/or fixed-wing aircraft to provide air mobility, reconnaissance, and support to ground forces.
-
E.
special operations aviation regiment
A special operations aviation regiment is a military aviation unit specialized in providing highly trained air support, insertion, extraction, and logistical capabilities for special operations forces in complex and high-risk environments.
- 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_69d8d38cc7948190a55ea64e5638994e |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:46 a.m.