Triple
T16025451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATEC |
E388706
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military testing organization |
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 testing organization Context triple: [ATEC, instanceOf, military testing organization]
-
A.
military capability development organization
A military capability development organization is an entity responsible for identifying future operational needs and systematically designing, testing, and integrating new doctrines, technologies, and force structures to enhance a military’s effectiveness.
-
B.
U.S. Army research organization
A U.S. Army research organization is a military institution responsible for conducting scientific and technological research, development, and experimentation to enhance the Army’s capabilities and readiness.
-
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.
weapons testing facility
A weapons testing facility is a secure, controlled site where weapons and related systems are developed, evaluated, and tested for performance, safety, and reliability.
-
E.
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.
- 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:55 a.m.