Triple
T19114140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commandant Instruction on uniforms |
E467862
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military uniform policy document |
C1851
|
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 uniform policy document Context triple: [Commandant Instruction on uniforms, instanceOf, military uniform policy document]
-
A.
military uniform regulation
chosen
Military uniform regulation is a set of formal rules and standards that govern the design, wear, appearance, and proper use of military uniforms and related insignia.
-
B.
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.
-
C.
military regulations
Military regulations are formal, authoritative rules and directives that govern the conduct, organization, procedures, and responsibilities of armed forces personnel and operations.
-
D.
service dress uniform
A service dress uniform is a formal military attire worn for official duties, ceremonies, and public appearances, typically featuring a tailored coat, trousers or skirt, and standardized insignia.
-
E.
military-adjacent uniformed service
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.
- 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:05 p.m.