Triple
T7009783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 504th Military Intelligence Brigade |
E162551
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military intelligence brigade |
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 intelligence brigade Context triple: [504th Military Intelligence Brigade, instanceOf, military intelligence brigade]
-
A.
missile defense brigade
A missile defense brigade is a military unit responsible for detecting, tracking, and intercepting incoming missile threats to protect designated forces, assets, and territories.
-
B.
U.S. Army aviation brigade
A U.S. Army aviation brigade is a large, modular combat unit that provides coordinated helicopter and unmanned aircraft support for assault, reconnaissance, transport, and logistical missions in support of ground forces.
-
C.
airborne infantry brigade
An airborne infantry brigade is a highly mobile, light infantry formation trained and equipped to deploy rapidly by air, including parachute or air assault operations, to seize and hold key objectives behind or ahead of enemy lines.
-
D.
military unit
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
-
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_69c6885928148190ae31909fbb5e9849 |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:34 p.m.