Triple
T2283782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia Army National Guard |
E51339
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state defense force |
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: state defense force Context triple: [Georgia Army National Guard, instanceOf, state defense force]
-
A.
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.
-
B.
state government
A state government is the political organization and administrative apparatus that exercises authority, creates and enforces laws, and provides public services within a specific subnational region of a country.
-
C.
state police agency
A state police agency is a government law enforcement organization with statewide jurisdiction responsible for enforcing laws, maintaining public order, and supporting local agencies across the entire state.
-
D.
paramilitary organization
A paramilitary organization is a structured group that operates with military-style training, hierarchy, and tactics but is not formally part of a recognized state's official armed forces.
-
E.
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.
- 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_69a88b08e4308190bdac9aebcca1c91a |
completed | March 4, 2026, 7:42 p.m. |
Created at: March 4, 2026, 7:48 p.m.