Triple
T25808701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kompani Linge |
E650045
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Norwegian military unit |
C30043
|
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: Norwegian military unit Context triple: [Kompani Linge, instanceOf, Norwegian military unit]
-
A.
Norwegian military personnel
Norwegian military personnel are individuals who serve in Norway’s armed forces, including the Army, Navy, Air Force, Home Guard, and associated support and special operations units, in defense of the nation and its interests.
-
B.
Norwegian Army garrison
A Norwegian Army garrison is a permanent military installation that houses, trains, and supports army units and personnel within Norway’s land forces structure.
-
C.
Finnish military formation
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.
-
D.
Royal Danish Air Force unit
A Royal Danish Air Force unit is an organizational entity within Denmark's air force responsible for specific operational, support, or administrative functions in national and international air missions.
-
E.
Norwegian resistance organization
chosen
A Norwegian resistance organization is a clandestine group formed to oppose and undermine occupying or oppressive forces in Norway through activities such as intelligence gathering, sabotage, and support for the civilian population.
- 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_69e7ab35d264819095367f7e80c983ff |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 7:07 a.m.