Triple
T16285624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ROK Army Aviation Command |
E395381
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military aviation command |
C37218
|
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 aviation command Context triple: [ROK Army Aviation Command, instanceOf, military aviation command]
-
A.
aviation command billet
An aviation command billet is a designated leadership position within an aviation organization responsible for directing, managing, and overseeing the operations, personnel, and resources of an aviation unit or command.
-
B.
regional air command
A regional air command is a military organizational unit responsible for planning, directing, and controlling air operations within a specific geographic area.
-
C.
air force commander
An air force commander is a senior military officer responsible for planning, directing, and overseeing air operations, personnel, and resources to achieve strategic and tactical objectives.
-
D.
special operations aviation command
A special operations aviation command is a military organization that provides specialized, often clandestine air support—such as infiltration, exfiltration, resupply, and close air support—for special operations forces in high-risk or sensitive missions.
-
E.
Tactical air force
A tactical air force is a military aviation organization focused on providing direct air support, interdiction, and battlefield air operations in coordination with ground and naval forces within a specific theater of operations.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:05 a.m.