Triple
T31439947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | uniformed services of the United States |
E802038
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | system of uniformed organizations |
C2423
|
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: system of uniformed organizations Context triple: [uniformed services of the United States, instanceOf, system of uniformed organizations]
-
A.
military organization
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.
military-adjacent uniformed service
chosen
A military-adjacent uniformed service is an organized, government-sanctioned body whose members wear standardized uniforms and perform defense-, security-, or support-related functions alongside or in coordination with the armed forces, but are not formally part of the military.
-
C.
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.
-
D.
military recruitment organization
A military recruitment organization is an entity responsible for attracting, evaluating, and processing individuals for enlistment or commissioning into a nation's armed forces.
-
E.
military uniform
A military uniform is a standardized set of clothing and accessories worn by armed forces personnel to signify rank, role, and affiliation while promoting discipline and unity.
- 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 9:04 p.m.