Triple
T12181856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Satakunnan lennosto |
E290239
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Finnish Air Force unit |
C20690
|
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: Finnish Air Force unit Context triple: [Satakunnan lennosto, instanceOf, Finnish Air Force unit]
-
A.
Finnish military formation
chosen
A Finnish military formation is an organized grouping of Finnish Defence Forces personnel and equipment, structured at various hierarchical levels (such as squad, platoon, company, battalion, brigade, or higher) to conduct coordinated military operations.
-
B.
Polish Air Force unit
A Polish Air Force unit is an organizational entity within Poland’s air arm responsible for operating, maintaining, and supporting assigned aircraft and air defense systems to fulfill national defense and allied mission objectives.
-
C.
Finnish Army formation
A Finnish Army formation is an organized military unit or grouping, such as a brigade or division, structured to conduct land operations under unified command within Finland’s defense forces.
-
D.
Belgian Air Force unit
A Belgian Air Force unit is an organizational entity within the Belgian Air Component responsible for executing specific air defense, support, training, or operational missions using assigned personnel, aircraft, and equipment.
-
E.
Belgian Air Force unit
A Belgian Air Force unit is an organizational subdivision of the Belgian Air Component, composed of personnel, aircraft, and equipment structured to perform specific operational, training, or support missions within national and allied defense frameworks.
- 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_69d6ab64de5881908d56eb7a75c6cc69 |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:50 p.m.