Triple
T33930997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 144th Armored Signal Company |
E869889
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. Army signal company |
C61335
|
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: U.S. Army signal company Context triple: [144th Armored Signal Company, instanceOf, U.S. Army signal company]
-
A.
United States Army signal brigade
A United States Army signal brigade is a specialized military unit responsible for planning, installing, operating, and maintaining tactical and strategic communications and information systems to support command and control across the battlefield.
-
B.
Quartermaster company
A quartermaster company is a military logistics unit responsible for supplying, transporting, and managing essential materials, equipment, and services to support combat and support forces.
-
C.
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.
-
D.
Operational Detachment Alpha
Operational Detachment Alpha is a small, highly trained U.S. Army Special Forces team designed to conduct specialized missions such as unconventional warfare, foreign internal defense, and special reconnaissance, often operating independently in austere environments.
-
E.
U.S. Army medical unit
A U.S. Army medical unit is a military organization that provides coordinated medical care, treatment, evacuation, and health support to soldiers and authorized personnel in both garrison and deployed operational environments.
- F. None of above. chosen
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_69f3499a59788190bff762a891471b31 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:49 a.m.