Triple
T2560415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commander of the Finnish Air Force |
E57228
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | air force commander role |
C4587
|
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: air force commander role Context triple: [Commander of the Finnish Air Force, instanceOf, air force commander role]
-
A.
major command of the United States Air Force
A major command of the United States Air Force is a large, top-level organizational unit responsible for directing and overseeing a broad functional or geographic segment of the Air Force’s mission, resources, and operations.
-
B.
major command of the Royal Air Force
A major command of the Royal Air Force is a high-level organizational formation responsible for directing and coordinating air operations, support, and resources within a defined functional or geographic area.
-
C.
United States Air Force position
chosen
A United States Air Force position is a defined role within the Air Force organizational structure that specifies an individual’s duties, responsibilities, rank requirements, and place in the chain of command to support the service’s mission.
-
D.
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.
-
E.
army commander post
An army commander post is a designated command facility or position from which a military commander directs, coordinates, and controls the operations of assigned forces.
- 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_69ab4a4ef9008190a0e6d4422b9418b7 |
completed | March 6, 2026, 9:42 p.m. |
Created at: March 6, 2026, 9:48 p.m.