Triple
T12983004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Roman Empire forces |
E321697
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | armed forces of a state |
C298
|
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: armed forces of a state Context triple: [Holy Roman Empire forces, instanceOf, armed forces of a state]
-
A.
military organization
chosen
A military organization is a structured group of armed forces personnel and resources, organized under a defined hierarchy and command system, to plan, coordinate, and conduct defense and combat operations in support of a state’s strategic objectives.
-
B.
defense organization
A defense organization is an entity, typically governmental or intergovernmental, responsible for planning, coordinating, and executing activities to protect a nation or group of nations from military and security threats.
-
C.
belligerent force
A belligerent force is an organized military or armed group that actively participates in hostilities during an armed conflict.
-
D.
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.
-
E.
military system
A military system is an organized structure of personnel, equipment, doctrines, and processes designed to plan, conduct, and support defense and combat operations.
- 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_69d8076479b8819090afce3591939cdf |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 8:39 p.m.