Triple
T29793271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brunswick auxiliary corps in British service |
E756469
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | auxiliary military corps |
C21918
|
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 corps Context triple: [Brunswick auxiliary corps in British service, instanceOf, auxiliary military corps]
-
A.
auxiliary military force
chosen
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.
auxiliary military personnel
Auxiliary military personnel are non-regular service members who provide specialized or supporting functions—such as logistics, medical aid, intelligence, or technical services—to enhance and sustain the operations of a primary armed force.
-
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.
military unit
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
- 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_69f22454583081908927516cb9938d1d |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 5:13 p.m.