Triple
T21773131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hiwis |
E537485
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | auxiliary military personnel |
C45268
|
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: auxiliary military personnel Context triple: [Hiwis, instanceOf, auxiliary military personnel]
-
A.
auxiliary military force
An auxiliary military force is a supplementary, often non-regular or part-time armed organization that supports a nation’s primary military through additional manpower, specialized skills, or local defense roles.
-
B.
military personnel category
A military personnel category is a classification that groups service members based on roles, ranks, duties, or service status within the armed forces.
-
C.
military administrative corps
A military administrative corps is a specialized branch of the armed forces responsible for managing personnel, logistics, finance, records, and other support functions that enable effective military operations.
-
D.
auxiliary air force
An auxiliary air force is a supplementary aviation component that supports a nation's primary air force through roles such as training, logistics, civil defense, and non-combat operations, often staffed by reservists or volunteers.
-
E.
American military personnel
American military personnel are individuals who serve in the United States Armed Forces, including the Army, Navy, Air Force, Marine Corps, Space Force, and Coast Guard, in roles ranging from combat and support to technical and administrative duties.
- 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_69e0c470759c819094a215757113562b |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:51 p.m.