Triple
T9294212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regular Force |
E223599
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military force component |
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: military force component Context triple: [Regular Force, instanceOf, military force component]
-
A.
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.
-
B.
component of land forces
A component of land forces is an organized, functionally distinct element of an army’s ground combat structure, such as infantry, armor, artillery, or support units, that contributes specific capabilities to land operations.
-
C.
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.
-
D.
full-time military force
A full-time military force is a permanently organized, professional body of armed personnel maintained by a state or authority, whose primary occupation is to train for, deter, and conduct military operations.
-
E.
component of the United States Armed Forces
A component of the United States Armed Forces is an organizational subdivision, such as a service branch, reserve, or specialized command, that contributes distinct capabilities and personnel to the nation’s overall military structure and 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_69ca8423edb08190bc0c91287a484768 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:35 p.m.