Triple
T29843001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 358th Brigade |
E757851
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | brigade-level unit |
C53553
|
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: brigade-level unit Context triple: [358th Brigade, instanceOf, brigade-level unit]
-
A.
U.S. Army infantry brigade
A U.S. Army infantry brigade is a modular, combined-arms combat unit typically consisting of several infantry battalions and supporting elements, organized to conduct sustained ground operations across a range of missions.
-
B.
regional military unit
A regional military unit is an organized group of armed forces assigned to operate within a specific geographic area, responsible for defense, security, and military operations in that region.
-
C.
U.S. Army brigade combat team
chosen
A U.S. Army brigade combat team is a modular, self-sustaining combined-arms formation, typically 3,000–5,000 soldiers, designed to conduct independent, full-spectrum operations as the Army’s primary tactical warfighting unit.
-
D.
Major Command Subordinate Unit
A Major Command Subordinate Unit is an organizational entity that operates under a major command, executing its directives and managing assigned missions, resources, and personnel within a defined scope of responsibility.
-
E.
U.S. Army battalion
A U.S. Army battalion is a mid-sized tactical unit, typically consisting of 300–1,000 soldiers organized into several companies, capable of independent operations under a battalion commander.
- 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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 5:40 p.m.