Triple
T7477196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Don’t Ask, Don’t Tell policy authorization |
E176660
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military personnel policy |
C7943
|
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 personnel policy Context triple: [Don’t Ask, Don’t Tell policy authorization, instanceOf, military personnel policy]
-
A.
military personnel category
A military personnel category is a classification that groups service members based on roles, ranks, duties, or service status within the armed forces.
-
B.
military personnel management agency
A military personnel management agency is an organization responsible for overseeing the recruitment, assignment, development, welfare, and separation of service members to ensure effective utilization and readiness of military human resources.
-
C.
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.
-
D.
military administration
Military administration is the organizational and managerial framework responsible for planning, directing, and overseeing the personnel, resources, logistics, and policies that enable a military force to function effectively.
-
E.
military regulations
chosen
Military regulations are formal, authoritative rules and directives that govern the conduct, organization, procedures, and responsibilities of armed forces personnel and 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_69c69f236ce08190a04d7679f03b29b2 |
completed | March 27, 2026, 3:15 p.m. |
Created at: March 27, 2026, 3:41 p.m.