Triple
T13968304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Army Signal Regiment units |
E335984
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military communications unit type |
C409
|
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 communications unit type Context triple: [U.S. Army Signal Regiment units, instanceOf, military communications unit type]
-
A.
military communications organization
chosen
A military communications organization is a structured unit responsible for planning, managing, and operating secure, reliable information and communication systems that support command, control, and coordination of military forces.
-
B.
military unit component
A military unit component is an individual sub-unit or element, such as a squad, platoon, or company, that combines with others to form a larger organized military force.
-
C.
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.
-
D.
communications unit
A communications unit is a modular component responsible for managing, formatting, and transmitting information between systems, devices, or subsystems using defined communication protocols.
-
E.
Wehrmacht signals unit
A Wehrmacht signals unit was a specialized German military formation responsible for establishing, operating, and maintaining communications networks—such as radio, telephone, and telegraph—between command elements and combat units during World War II.
- 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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:18 p.m.